unofficial mirror of emacs-devel@gnu.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 06:57:48 -0800	[thread overview]
Message-ID: <24524.61804.293057.859729@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <83k0tvbi0u.fsf@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"Eli Zaretskii writes:
 > > From: "T.V Raman" <raman@google.com>
 > > Date: Sat,  5 Dec 2020 19:35:17 -0800 (PST)
 > > 
 > >    3. You invoke pop-global-mark (C-x C-SPC) and as you cycle through,
 > >       hit the mark in the info buffer.
 > > 
 > >       If you happen to have changed nodes in the info buffer after you
 > >       set the mark earlier, you get this error message --- which is
 > >       annoying:
 > > 
 > >       Global mark position is outside accessible part of buffer 
 > 
 > What would you like to happen instead? the message is factually
 > correct.

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

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



  reply	other threads:[~2020-12-06 14:57 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=24524.61804.293057.859729@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).