From: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org
Subject: Newsreader citation interface
Date: Sat, 05 Mar 2005 09:17:02 +0900 [thread overview]
Message-ID: <87zmxj7xq9.fsf_-_@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <d0ah7d$gfa$1@shpxurnq.databasix.com> (Russell B.'s message of "Fri, 04 Mar 2005 12:42:21 -0800")
Russell B <bigfunchy@databasix.com> writes:
> There is nothing repressive about those rules; they only exist to
> protect all users from a collective action problem, namely that of
> individual users who are tempted to do things--like leaving whitespace
> before the quote marker, or posting responses above the quoted text
> ("top-posting")--that would disrupt the flow of the discussion and
> cause unexpected behavior in standard newsreaders.
I'd think that about 80% of the problem is automatic insertion of entire
quoted posts by the newsreader software during a followup, and many
users being too lazy/clueless to delete it. Right?
I've often wondered if there's a better user interface for citing the
replied-to post, which would make "proper" citation so easy that
everybody would do it without thinking.
For instance, consider the following:
* You always start out with an empty body, no quoted text is ever
inserted.
* You have some key bound to `insert-next-cited-line', which keeps
track of the last cited line you inserted. The first time you use
this key, it inserts the ".... wrote:" line, and the first quoted
text line, and each subsequent press inserts one more line, and
increments the `next-to-be-inserted' line number.
You can repeat this key to quickly insert regions of quoted text.
* You have another key bound to `uninsert-last-cited-line' which just
undoes the effect of "insert-next-cited-line": it deletes the last
inserted line, and decrements the `next-to-be-inserted' line number,
so that you can reinsert that line later (presumably after you've
typed some text in between).
* There's a final key bound to `shift-last-cited-line', which deletes
the last inserted line of quoted text, and then does
`insert-next-cited-line'.
This key is for when you want to skip parts of the message that
shouldn't be inserted.
I'm not sure how this sort of interface would be in practice, but it
sounds very convenient to "scan out" regions of quoted text and be able
to insert your answers in between. [Unfortunately I suppose any
interface using actual key bindings is unacceptable to a large portion
of the populace... sigh.]
-Miles
--
Run away! Run away!
next parent reply other threads:[~2005-03-05 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d06pjt$iq$1@bwahahahaha.databasix.com>
[not found] ` <4227C176.7050601@mungo.com>
[not found] ` <d09kop$34s$1@fluffy.databasix.com>
[not found] ` <4228811A.6030703@mungo.com>
[not found] ` <d0ah7d$gfa$1@shpxurnq.databasix.com>
2005-03-05 0:17 ` Miles Bader [this message]
[not found] ` <d0b95g$fq4$1@m3t00.databasix.com>
2005-03-05 7:48 ` Miles Bader
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=87zmxj7xq9.fsf_-_@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@gnu.org \
--cc=ding@gnus.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.
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).