From: Drew Adams <drew.adams@oracle.com>
To: 19930@debbugs.gnu.org
Subject: bug#19930: 25.0.50; REGRESSION: accessing minibuffer from 2nd frame for same buffer scrolls window back to point of 1st frame
Date: Mon, 23 Feb 2015 11:19:26 -0800 (PST) [thread overview]
Message-ID: <c1df2094-8a49-41a7-a5e3-d32b4b0bfb36@default> (raw)
This regression was introduced in Emacs 24.3. There is no such problem
in Emacs 20 through 24.2.
To reproduce:
1. runemacs.exe -Q --debug-init -l "onetest.el" -f "1on1-emacs"
File onetest.el is attached.
This opens Emacs with a standalone minibuffer frame.
2. Visit a file with some text in it, say foo.el, in the original
(non-minibuffer) frame displayed.
3. Put point on some function name, e.g. near bob.
3. C-x 5 2, so you now have two frames showing the same buffer.
4. In the frame just created, scroll down a ways (or otherwise move down
- it is unimportant how you do this), and put point on some other
symbol (name).
5. M-x grep RET
As soon as you hit RET, the current window (in the second frame)
scrolls back to the point position of the first frame. And if you
then use M-n to grab a name at point for `grep', it grabs the symbol
name under the point for the other frame.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2015-02-23 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 19:19 Drew Adams [this message]
2018-06-06 1:02 ` bug#19930: 25.0.50; REGRESSION: accessing minibuffer from 2nd frame for same buffer scrolls window back to point of 1st frame Noam Postavsky
2018-06-06 2:41 ` Eli Zaretskii
[not found] <<c1df2094-8a49-41a7-a5e3-d32b4b0bfb36@default>
[not found] ` <<87zi084the.fsf@gmail.com>
[not found] ` <<837encab6p.fsf@gnu.org>
2018-06-06 4:51 ` Drew Adams
2018-06-06 11:50 ` Noam Postavsky
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=c1df2094-8a49-41a7-a5e3-d32b4b0bfb36@default \
--to=drew.adams@oracle.com \
--cc=19930@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).