unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: Rethinking count-words-region
Date: Fri, 07 Oct 2011 22:29:31 +0200	[thread overview]
Message-ID: <4E8F612B.1060401@online.de> (raw)
In-Reply-To: <87vcs0q05l.fsf@stupidchicken.com>

Am 07.10.2011 17:41, schrieb Chong Yidong:
> The command `count-words-region', newly introduced for Emacs 24, is
> inconsistent with the pre-existing `count-lines-region'.  If no region
> is active, the former reports the number of words in the buffer
> (implemented in Bug#9429).  The latter always reports the number of
> lines in the region, whether or not it is active.
>
> The two ought to be consistent.  The behavior of `count-words-region' is
> the better one, I think, even if adopting it incurs some backward
> incompatibility.
>
> But going beyond this, instead of introducing a separate
> `count-words-region' command, why not fold this functionality into
> `count-lines-region'?  After all, `count-lines-region' already reports
> the number of characters, and there's space for it to report the number
> of words too.  And it has a convenient binding in M-=, whereas
> `count-words-region' has no default binding.
>
> Maybe we could rename the combined function something like `count-text'
> (better suggestions welcome).
>
>

Hi,

simply "count-words", "count-lines" seems better for me.
A lot of other function restrict to region already, if active.
User may assume that.

When -region is mentioned explicitly, it should require it, not operate 
on the whole buffer.

Cheers,

Andreas




  parent reply	other threads:[~2011-10-07 20:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 15:41 Rethinking count-words-region Chong Yidong
2011-10-07 16:46 ` Jambunathan K
2011-10-08 16:53   ` Chong Yidong
2011-10-08 18:00     ` Andreas Röhler
2011-10-07 18:08 ` Eli Zaretskii
2011-10-07 20:51   ` Chong Yidong
2011-10-07 20:55     ` Chong Yidong
2011-10-08 17:58       ` Andreas Röhler
2011-10-08 18:11         ` Drew Adams
2011-10-08 18:23           ` Chong Yidong
2011-10-08 18:25             ` Drew Adams
2011-10-08 18:29               ` Alan Mackenzie
2011-10-08 19:04                 ` Lars Ingebrigtsen
2011-10-08 19:28                 ` Juri Linkov
2011-10-08 18:40             ` Andreas Röhler
2011-10-08  6:22     ` Eli Zaretskii
2011-10-07 20:29 ` Andreas Röhler [this message]
2011-10-07 20:55 ` Alan Mackenzie
2011-10-08 16:52 ` Chong Yidong
2011-10-08 17:51   ` Andreas Röhler
2011-10-08 20:04   ` Juri Linkov
2011-10-08 20:46     ` Chong Yidong
2011-10-08 21:09       ` Juri Linkov
2011-10-08 20:49     ` Drew Adams
2011-10-08 21:12       ` Juri Linkov
2011-10-08 21:33         ` Drew Adams
2011-10-09  0:57           ` chad
2011-10-09  1:05             ` Drew Adams

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=4E8F612B.1060401@online.de \
    --to=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.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).