Gnus development mailing list
 help / color / mirror / Atom feed
From: Matt Armstrong <matt@lickey.com>
Cc: Karl Eichwalder <keichwa@gmx.net>,
	Sean Neakums <sneakums@zork.net>,
	ding@gnus.org
Subject: Re: Annoying new features in newer Oorts
Date: Fri, 03 May 2002 15:30:32 -0600	[thread overview]
Message-ID: <874rhozzpj.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <vafpu0dazny.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 03 May 2002 19:50:41 +0200")

(if I've sent this twice, disregard the first and read this one, sorry)

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Karl Eichwalder <ke@gnu.franken.de> writes:
>
>> The question simply is: where does a header line start?  Some of us
>> think it starts in column 0, others think it starts after ": ".  Both
>> parties are "right"; in those case it's good habbit to leave things as
>> are.
>
> This is not the question, IMHO.  The question is, when in a header,
> what would be a convenient place for C-a to go to?  And the current
> behavior gets you to the colon with one C-a, and to the beginning of
> the line with two C-a.  The old behavior got you to the beginning to
> the line with one C-a, but getting to the colon was difficult.
>
> One could try to make a user option, but given the existence of
> define-key, this seems a bit superfluous.

I notice that C-a toggles between the end of line and just after the
colon.  Could we change C-a to go to the beginning of the line first
and to the colon when already there?  This way you'd do C-a C-a to get
the magical behavior and people's hard coded brain pathways would not
be strained as hard.

I like the magical behavior, but I have found it hard to retrain my
brain.  I seem to always end up killing a header line while not
actually being at the beginning of the line.

The other instances of "magical C-a" in Emacs that I'm aware of are
all cases where a shell or program prompt is displayed.  It arguably
never makes sense to go the left past a prompt, while it does make
sense to do so in the message header.


Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> WINI C-a in body could have added magic, too?  In a cited line, it
> could go to the end of the ">>" prefix.

Ditto Josh's comments here.


-- 
Don't send mail to Marcia.Smith@hole.lickey.com
The address is there for spammers to harvest.




  parent reply	other threads:[~2002-05-03 21:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3229147191814452@oakhurst.yi.org>
2002-04-30  9:34 ` Sean Neakums
     [not found]   ` <3229150801659975@oakhurst.yi.org>
2002-04-30 11:14     ` Romain FRANCOISE
2002-04-30 11:53       ` Fabien Penso
2002-04-30 11:39     ` Matthieu Moy
2002-04-30 11:48       ` Sean Neakums
     [not found]       ` <3229343185064781@oakhurst.yi.org>
2002-05-02 15:49         ` Sean Neakums
2002-05-02 16:32           ` Karl Eichwalder
2002-05-02 17:59             ` Florian Weimer
2002-05-03  7:38             ` Sean Neakums
2002-05-03 15:05               ` Karl Eichwalder
2002-05-03 17:50                 ` Kai Großjohann
2002-05-03 21:23                   ` Matt Armstrong
2002-05-03 21:30                   ` Matt Armstrong [this message]
2002-05-04  1:19                     ` Karl Eichwalder
2002-05-04 13:48                     ` Sean Neakums
2002-05-04 14:01                       ` Florian Weimer
2002-05-04 14:05                         ` Sean Neakums
2002-05-05 12:02                     ` Kai Großjohann
2002-05-05 13:29                     ` Steinar Bang
2002-05-05 15:18                       ` Simon Josefsson
2002-05-05 13:19               ` Steinar Bang
2002-05-05 13:14     ` Steinar Bang
2002-04-30 11:10 ` Martin Sandiford
2002-04-30 11:11 ` Kai Großjohann
2002-05-14 10:48   ` Andreas Fuchs
2002-05-14 14:30   ` Mark Thomas
2002-05-14 14:54     ` Andreas Fuchs
2002-05-14 15:24     ` Kai Großjohann
2002-04-30 13:05 ` 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=874rhozzpj.fsf@squeaker.lickey.com \
    --to=matt@lickey.com \
    --cc=ding@gnus.org \
    --cc=keichwa@gmx.net \
    --cc=sneakums@zork.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).