From: Chong Yidong <cyd@gnu.org>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>
Cc: 9959@debbugs.gnu.org
Subject: bug#9959: 24.0.90; `count-words' command from a narrowed buffer
Date: Wed, 18 Jul 2012 22:32:38 +0800 [thread overview]
Message-ID: <87txx52l89.fsf@gnu.org> (raw)
In-Reply-To: <j9d04n$aoq$1@dough.gmane.org> (Kevin Rodgers's message of "Tue, 08 Nov 2011 21:39:06 -0700")
Kevin Rodgers <kevin.d.rodgers@gmail.com> writes:
> On 11/6/11 8:34 AM, Drew Adams wrote:
>
>> 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
>
> If I've narrowed a very large buffer to a small region, I am not interested in
> the counts for the entire buffer nor willing to wait for them.
Agreed. I committed the simplest version, i.e. reporting "Narrowed part
of buffer" in the message. I'll leave this open in case as a wishlist
item; if anyone wants to implement the more complicated reporting with
C-u, feel free.
next prev parent reply other threads:[~2012-07-18 14:32 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
2012-07-18 14:32 ` Chong Yidong [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txx52l89.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=9959@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.