Re: pop-global-mark and info buffers

[T.V Raman]

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 
>> From: "T.V Raman" <raman@google.com>
>> Date: Sun, 6 Dec 2020 06:57:48 -0800
>> Cc: raman@google.com,
>>     emacs-devel@gnu.org
>> 
>> The message may be factually correct but useless. It could in the
>> least tell you the buffer where the mark is "out of reach"
>
> Thanks, I added the buffer name to the error message for Emacs 28.

-- 

Thanks,

--Raman
?7?4 Id: kg:/m/0285kf1  ?0?8