From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 'Kevin Rodgers' <kevin.d.rodgers@gmail.com>, 9959@debbugs.gnu.org
Subject: bug#9959: 24.0.90; `count-words' command from a narrowed buffer
Date: Wed, 9 Nov 2011 08:51:15 -0800 [thread overview]
Message-ID: <C4724B038C7B45A3B9C3D3E681B128AC@us.oracle.com> (raw)
In-Reply-To: <87obwlntge.fsf@mail.jurta.org>
> > Another possibility: Do as we do with `apropos' commands.
> > We have both a prefix arg and a user option,
> > `apropos-do-all', that affect the behavior, with the less
> > complete, and faster, behavior as the default.
>
> Or
It's not an "or" - the two are orthogonal (except for key binding
choice/conflict). I was talking about how much info is shown. You're talking
about where the info is displayed.
The `apropos' approach is good because it lets users define a personal
preference that might be for seeing more info (=t), yet it also lets users
change the behavior on the fly using a prefix arg.
> do as we do with `what-cursor-position' (`C-x =') that
> prints info in the echo area, but with prefix argument shows
> full details in *Help* buffer.
I don't see the output of even the full info as being something voluminous,
necessitating *Help*. But perhaps you had something more in mind. The info
we've discussed so far should be OK for the minibuffer.
next prev parent reply other threads:[~2011-11-09 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 10:28 bug#9959: 24.0.90; `count-words' command from a narrowed buffer Dani Moncayo
2011-11-06 15:01 ` Juri Linkov
2011-11-06 15:34 ` Drew Adams
2011-11-06 16:30 ` Juri Linkov
2011-11-06 17:30 ` Drew Adams
2011-11-09 4:39 ` Kevin Rodgers
2011-11-09 15:05 ` Drew Adams
2011-11-09 16:01 ` Drew Adams
2011-11-09 16:36 ` Juri Linkov
2011-11-09 16:51 ` Drew Adams [this message]
2012-07-18 14:32 ` Chong Yidong
2022-02-13 9:56 ` Lars Ingebrigtsen
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=C4724B038C7B45A3B9C3D3E681B128AC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9959@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=kevin.d.rodgers@gmail.com \
/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).