From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>, "'Dani Moncayo'" <dmoncayo@gmail.com>
Cc: 9959@debbugs.gnu.org
Subject: bug#9959: 24.0.90; `count-words' command from a narrowed buffer
Date: Sun, 6 Nov 2011 07:34:58 -0800 [thread overview]
Message-ID: <92DCBADB54F446EF9E76A3A6E723C239@us.oracle.com> (raw)
In-Reply-To: <87aa89uwfp.fsf@mail.jurta.org>
> > The message should begin with something like
> > "Buffer (narrowed part) has ...".
>
> Like `C-x =' displays information about a narrowed buffer
> in angle brackets `<...>', `count-words' could do the same
> and display both widened and narrowed counts.
FWIW, in Emacs generally, "buffer (narrowed part)" is referred to as the buffer
"restriction".
But I'm not sure that users unfamiliar with the term would understand it
immediately in a prompt. Same potential problem with an unexplained convention
such as `<...>'. I don't have a better suggestion, however. So far, I'd lean
toward, "Buffer restriction has 112 lines, 673 words, 6074 chars"
Or maybe both counts could be shown, making it a bit clearer what the info is?
"Buffer (restriction): 1135 (112) lines, 6894 (673) words, 70452 (6074) chars".
And in that case, maybe "Buffer (narrowed)..." would be better. Another
possibility (shorter):
Narrowed/total: 112/1135 lines, 673/6894 words, 6074/70452 chars
next prev parent reply other threads:[~2011-11-06 15:34 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 [this message]
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
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=92DCBADB54F446EF9E76A3A6E723C239@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9959@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=juri@jurta.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).