From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: [bug] Mark limit score
Date: Sat, 20 Oct 2001 15:57:04 +1000 [thread overview]
Message-ID: <87elnyhn0v.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <vaflmi7zwqb.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 19 Oct 2001 13:37:48 +0200")
On Fri, 19 Oct 2001, Kai Großjohann wrote:
> Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
>
>> What do you think about this:
>>
>>
>> --- lisp/gnus-sum.el Thu Oct 18 20:03:02 2001
>> +++ /cygdrive/c/Programme/XEmacs/xemacs-packages/lisp/gnus/gnus-sum.el
[...]
> If I understand correctly, this means that calling
> gnus-summary-limit-to-score without specifying a score via the prefix
> arg means that the user is prompted.
>
> It's not clear to me that this is a good idea: C-d does not prompt you
> how many characters to delete, either, it just deletes 1 character
> unless you specify otherwise.
Control-D is operating in an environment where there is only *one*
possible thing that you want it to do: delete the character following
point.
You can *repeat* this operation several times if you wish, getting the
same effect each time.
By contrast, there is a broad range of scores in the average Gnus
buffer[1] that the user may mean when they request a 'narrow to score'.
Also, limit to sender, limit to subject and friends don't have any
default that they use, for precisely the same reason: it's *not* clear
which value the user meant.
Finally, I support this change because every single time I have used
narrow to score I have ended up spitting and cursing at Gnus for being a
brain-dead, stupid thing that has a crazy-ass default on that command.
I suspect that I am not alone in this. :)
Daniel
Footnotes:
[1] Assuming that most Gnus buffers have scoring like mine or more
advanced.
--
Most of the luxuries and many of the so-called comforts of life, are not only
not indispensable, but positive hindrances to the elevation of mankind.
-- Henry David Thoreau, _Walden_, "Economy" [1854]
next prev parent reply other threads:[~2001-10-20 5:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 9:47 Frank Schmitt
2001-10-18 10:00 ` Björn Torkelsson
2001-10-18 19:51 ` Simon Josefsson
2001-10-18 22:32 ` Frank Schmitt
2001-10-19 11:37 ` Kai Großjohann
2001-10-19 12:42 ` Frank Schmitt
2001-10-20 5:57 ` Daniel Pittman [this message]
2001-10-20 11:26 ` Kai Großjohann
2001-10-20 11:51 ` Frank Schmitt
2001-10-20 13:15 ` Frank Schmitt
2001-10-20 18:18 ` Kai Großjohann
2001-10-20 18:40 ` Frank Schmitt
2001-10-20 22:01 ` Kai Großjohann
2001-10-20 22:26 ` Frank Schmitt
2001-10-20 22:20 ` Frank Schmitt
2001-10-21 8:36 ` Kai Großjohann
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=87elnyhn0v.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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 NNTP newsgroup(s).