Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Gary Johnson <garyjohn@spocom.com>
Cc: gdb@sourceware.org
Subject: Re: [PATCH] Fix 5-line offset of edit command
Date: Sun, 12 Feb 2023 08:14:50 +0200	[thread overview]
Message-ID: <83edqvif51.fsf@gnu.org> (raw)
In-Reply-To: <20230211225233.GB17240@phoenix> (message from Gary Johnson on Sat, 11 Feb 2023 14:52:33 -0800)

> Date: Sat, 11 Feb 2023 14:52:33 -0800
> From: Gary Johnson <garyjohn@spocom.com>
> 
> > > The problem appears to be in the edit_command() function in
> > > cli-cmds.c, at line 966 in version 12.1.  The solution is to
> > > delete that line.  The patch is below.
> > 
> > This is probably editor-specific?
> 
> No, it's not editor-specific.  The command to run the editor is
> created at the end of the edit_command() function:

I meant the effect is editor-specific.  IOW, what exactly does each
editor display when passed a line number.

> As I recall, this used to work long ago, then something changed and
> the editor was always opened at line 6, then around 2020 it changed
> again to open at the current line plus 5.  I suspect
> a copy-and-paste error, but I haven't looked into the history of
> that function.

I tried to look into the history with "git log -L", but got stuck at
the commit that moved the function from another file.  Maybe some Git
expert could suggest how to cross that line?

> I intended to send this to gdb-patches, but it looks like I wasn't
> paying attention to the address and sent it to the general gdb list
> instead.

Yes, it is best to resent to gdb-patches.

  reply	other threads:[~2023-02-12  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 10:08 Gary Johnson
2023-02-11 10:58 ` Eli Zaretskii via Gdb
2023-02-11 22:52   ` Gary Johnson
2023-02-12  6:14     ` Eli Zaretskii via Gdb [this message]
2023-02-12  9:23       ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83edqvif51.fsf@gnu.org \
    --to=gdb@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=garyjohn@spocom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox