From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: C-x C-f in two frames -> "user minibuffer while in
Date: Thu, 07 Jul 2005 10:57:08 +0200 [thread overview]
Message-ID: <7eoe9f2duj.fsf@ada2.unipv.it> (raw)
In-Reply-To: u1x6brsi6.fsf@comcast.net
don provan <dprovan@comcast.net> writes:
> Has anyone come up with any ways the recursive commands could be
> better, or is it pretty much accepted that there's nothing that could
> be done to improve them?
one idea is to modify `mode-line-format' to indicate presence, level,
or stack contents, of recursion.
presence: R
level: RRR (or maybe R3)
stack contents: (find-file find-file find-file)
alternatively, borrow something from the recursive editing indicator
(normally square braces around the major and minor mode info).
nothing is univerally "pretty much accepted" (except death and taxes,
but i hear emacs and the fsf avoid these, respectively, somehow :-).
thi
next prev parent reply other threads:[~2005-07-07 8:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 13:18 C-x C-f in two frames -> "user minibuffer while in minibuffer": Bug? David Reitter
2005-06-08 14:08 ` Peter Dyballa
[not found] ` <mailman.3863.1118240186.25862.help-gnu-emacs@gnu.org>
2005-06-08 14:55 ` C-x C-f in two frames -> "user minibuffer while in Toto
2005-07-03 21:47 ` David Combs
2005-07-04 0:15 ` Miles Bader
[not found] ` <mailman.2058.1120436940.2857.help-gnu-emacs@gnu.org>
2005-07-04 7:52 ` don provan
2005-07-05 22:27 ` Miles Bader
[not found] ` <mailman.2259.1120602813.2857.help-gnu-emacs@gnu.org>
2005-07-07 7:21 ` don provan
2005-07-07 8:57 ` Thien-Thi Nguyen [this message]
2005-07-07 15:10 ` Drew Adams
2005-07-04 8:23 ` David Kastrup
2005-06-09 16:22 ` C-x C-f in two frames -> "user minibuffer while in minibuffer": Bug? Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2005-07-04 10:01 C-x C-f in two frames -> "user minibuffer while in LENNART BORGMAN
[not found] <mailman.2091.1120471829.2857.help-gnu-emacs@gnu.org>
2005-07-05 7:12 ` don provan
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=7eoe9f2duj.fsf@ada2.unipv.it \
--to=ttn@glug.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.
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).