unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 32777@debbugs.gnu.org
Subject: bug#32777: 27.0.50; window-buffer gets wrong point
Date: Thu, 20 Sep 2018 01:55:01 +0300	[thread overview]
Message-ID: <87musd9lc2.fsf@mail.linkov.net> (raw)

This bug report concerns one particular usage of window-buffer in
read-extended-command, but the same issue might exist in other places:

0. emacs -Q

1. copy to *scratch* as text:

next-error
nonexistent-command

2.

2.1. put point on "next-error", type M-x M-n,
     it correctly inserts "next-error" to the minibuffer

2.2. put point on "nonexistent-command", type M-x M-n,
     it correctly displays "End of history; no default available"

3.

3.1. put point on "nonexistent-command"

3.2. split window C-x 2 or C-x 3 and switch to another window C-x o

3.3. put point on "next-error", type M-x M-n,
     it correctly inserts "next-error" to the minibuffer

4.

4.1. delete-other-windows with C-x 1

4.1. put point on "nonexistent-command"

4.2. create new frame with C-x 5 2

4.3. put point on "next-error", type M-x M-n,
     it displays "End of history; no default available",
     this is wrong





             reply	other threads:[~2018-09-19 22:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 22:55 Juri Linkov [this message]
2018-09-30  4:03 ` bug#32777: 27.0.50; window-buffer gets wrong point Federico Tedin
2018-10-02  2:07   ` Federico Tedin
2018-10-02  3:21     ` Eli Zaretskii
2018-10-02 12:31       ` Federico Tedin
2018-10-13  9:19         ` Eli Zaretskii
2018-10-13 13:08           ` martin rudalics
2018-10-15  7:56             ` martin rudalics
2018-12-21  0:18               ` Juri Linkov
2018-12-21  9:15                 ` martin rudalics
2018-12-21 16:02                   ` Eli Zaretskii
2018-12-23  9:40                     ` martin rudalics
2018-12-29  9:59                       ` martin rudalics
2018-12-29 23:10                         ` Juri Linkov
2018-12-30  9:49                           ` martin rudalics

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=87musd9lc2.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=32777@debbugs.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).