From: Juri Linkov <juri@jurta.org>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: 16214@debbugs.gnu.org, josh@foxtail.org, roland@hack.frob.com
Subject: bug#16214: Consistency in dired-, occur-, and grep-mode
Date: Mon, 23 Dec 2013 23:52:42 +0200 [thread overview]
Message-ID: <87fvpj5voe.fsf@mail.jurta.org> (raw)
In-Reply-To: <20131223.203459.187619082.tkk@misasa.okayama-u.ac.jp> (Tak Kunihiro's message of "Mon, 23 Dec 2013 20:34:59 +0900 (JST)")
> Assigning <RET> to (open-file-this-window) on occur/grep may loose
> convenience, but helps new users because that behavior is similar to
> following hyperlink in a web browser.
This behavior is similar to using History or Bookmarks window
in a web browser. For example, in Firefox typing `C-h' opens
the History list in the left side window (and C-b opens the
Bookmark list in the left side window). In the side window
you can press <RET> or click on a link name, and it will open
another page in the main window, replacing old page with a new
page. This is exactly like <RET> works in grep/occur buffers.
> A. edit-buffer
> To avoid overwriting `e' in dired, it seems that `C-x C-q' is the
> second choice. Is `M-e' or `M-g e' better?
Adding a new key is not better because it will be incompatible
with older versions.
> D. open-file-this-window
> Other candidates besides <RET> would be something like `M-<RET>' or 'M-o'?
For a key to use for this-window you could look at `C-x C-b' (list-buffers)
that binds the key `f' to `Buffer-menu-this-window'.
next prev parent reply other threads:[~2013-12-23 21:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 13:40 bug#16214: Consistency in dired-, occur-, and grep-mode Tak Kunihiro
2013-12-21 19:23 ` Drew Adams
2013-12-21 20:15 ` Josh
2013-12-21 21:30 ` Juri Linkov
2013-12-22 11:48 ` Tak Kunihiro
2013-12-22 21:44 ` Juri Linkov
2013-12-23 11:34 ` Tak Kunihiro
2013-12-23 21:52 ` Juri Linkov [this message]
2013-12-24 23:15 ` Tak Kunihiro
2013-12-25 20:57 ` Juri Linkov
2013-12-28 9:57 ` Tak Kunihiro
2022-02-10 8:27 ` Lars Ingebrigtsen
2022-02-10 9:26 ` Tak Kunihiro
2022-02-10 11:37 ` Lars Ingebrigtsen
2022-02-11 5:54 ` Tak Kunihiro
2022-02-12 3:57 ` Richard Stallman
2022-02-12 8:16 ` Michael Albinus
2022-02-14 4:13 ` Richard Stallman
2022-02-14 6:52 ` Michael Albinus
2022-02-15 4:30 ` Richard Stallman
2022-02-12 19:12 ` Howard Melman
2022-02-12 20:43 ` Howard Melman
2022-02-14 4:14 ` Richard Stallman
2022-02-17 16:28 ` Howard Melman
2022-02-17 17:12 ` bug#16214: [External] : " Drew Adams
2022-02-20 1:43 ` Tak Kunihiro
2022-02-20 18:17 ` Howard Melman
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=87fvpj5voe.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=16214@debbugs.gnu.org \
--cc=josh@foxtail.org \
--cc=roland@hack.frob.com \
--cc=tkk@misasa.okayama-u.ac.jp \
/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).