all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: eliz@gnu.org
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: pop-global-mark and info buffers
Date: Sun, 6 Dec 2020 17:17:09 -0800	[thread overview]
Message-ID: <24525.33429.29554.587022@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <83czzmadfm.fsf@gnu.org>

I haven't pulled and rebuilt yet :-)Eli Zaretskii writes:
 > > From: "T.V Raman" <raman@google.com>
 > > Cc: emacs-devel@gnu.org
 > > Date: Sun, 06 Dec 2020 12:15:45 -0800
 > > 
 > > Eli Zaretskii <eliz@gnu.org> writes:
 > > 
 > > Thinking more about this:
 > > 
 > > 1.As a long time Emacs user, I suspect I almost never set the mark in
 > > info buffers which is likely why I never got bitten by this.
 > > 
 > > 2. The mark ring -- both local and global mark rings are powerful
 > >    features but not very approachable to a new Emacs user, and this
 > >    specific bug likely will drive at least some of them away.
 > > 
 > >    3. The fix to the error message will help, but it may be possible to
 > >       do more for the user, e.g. if the marker is outside the narrowed
 > >       portion of a buffer, widen and then jump there? We could also
 > >       special case info so that we widen, jump and narrow to the node
 > >       containing the marker.
 > > 
 > >       4. If we dont do 3, perhaps we could in the least jump to the
 > >          buffer containing the mark, and change the error to a warning
 > >          message that tells the user to widen the visible portion of the
 > >          buffer and then tell him how to jump there after widening 
 > 
 > There's a variable widen-automatically, did you try to use it?

-- 
♉Id: kg:/m/0285kf1  🦮♉

--
♉Id: kg:/m/0285kf1  🦮♉



  reply	other threads:[~2020-12-07  1:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06  3:35 pop-global-mark and info buffers T.V Raman
2020-12-06  5:49 ` Eli Zaretskii
2020-12-06 14:57   ` T.V Raman
2020-12-06 15:42     ` Arch linux patches Ergus
2020-12-06 16:03       ` Eli Zaretskii
2020-12-06 15:44     ` pop-global-mark and info buffers Eli Zaretskii
2020-12-06 15:55       ` T.V Raman
2020-12-06 20:15       ` T.V Raman
2020-12-06 20:26         ` Eli Zaretskii
2020-12-07  1:17           ` T.V Raman [this message]
2020-12-07  3:40             ` Eli Zaretskii
2020-12-07 14:52               ` T.V Raman
2020-12-07 16:05                 ` Eli Zaretskii
2020-12-07 20:28                   ` T.V Raman
2020-12-06  6:11 ` Drew Adams

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=24525.33429.29554.587022@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.