From: David Z Maze <dmaze@mit.edu>
To: info-gnus-english@gnu.org
Subject: Re: posting name in summary buffer
Date: Wed, 24 Jan 2007 10:33:06 -0500 [thread overview]
Message-ID: <y68tzygtp71.fsf@department-of-alchemy.mit.edu> (raw)
In-Reply-To: <pe8k84-26l.ln1@news.tdc.dk>
hotmail_spam@hotmail.com (Martin Jørgensen) writes:
>>>>>> "Adam" == Adam Sjøgren <asjo@koldfront.dk> writes:
>
> Adam> On Tue, 23 Jan 2007 08:59:00 +0100, Martin wrote:
> >> Thanks. I will consider that but I'm not sure how it should
> >> confuse readers. I think it looked very clear who wrote what...
>
> Adam> Maybe people care less now - as they seem to do with
> Adam> top-posting - I used to be flamed for using the "Name>"-style;
> Adam> after a while I came to the conclusion that it wasn't worth
> Adam> the trouble.
>
> Aha.... I'll just watch and see what people think about this posting
> style and if they get too annoyed, I'll stop again...
I had a passing fling with Supercite several years ago. I stopped
mostly because my citations looked different from everyone else's, and
the styles didn't really play well together. The style I really
wanted was a composite indent-and-attribute style like
Adam> second-level post
MJ> Your reply to adam.
DZM> If only Supercite did what I wanted!
The other problem I never figured out how to solve is filling in
"other" attributions -- where you quote Adam quoting you, the ">>"
should get replaced with your own initials, but that involves some
logic capable of searching the article history and figuring that out.
> BTW: Where does all that white-space in the beginning of my citation
> come from? Hmm.... I only added these 3 lines to my .emacs:
>
> (autoload 'sc-cite-original "supercite" "Supercite 3.1" t)
> (autoload 'sc-submit-bug-report "supercite" "Supercite 3.1" t)
> (setq message-cite-function 'sc-cite-original)
My guess is sc-citation-leader, poking at some variables.
--dzm
next prev parent reply other threads:[~2007-01-24 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 7:29 Gernot Hassenpflug
2007-01-20 10:46 ` Gernot Hassenpflug
2007-01-20 11:50 ` Adam Sjøgren
2007-01-20 13:54 ` Gernot Hassenpflug
2007-01-20 23:07 ` Martin Jørgensen
2007-01-21 0:11 ` Adam Sjøgren
2007-01-21 10:36 ` Martin Jørgensen
2007-01-21 11:13 ` Charles philip Chan
2007-01-21 12:47 ` Adam Sjøgren
2007-01-21 15:25 ` Springfield
2007-01-21 20:34 ` Adam Sjøgren
2007-01-23 7:59 ` Martin Jørgensen
2007-01-23 17:33 ` Adam Sjøgren
2007-01-24 14:52 ` Martin Jørgensen
2007-01-24 15:33 ` David Z Maze [this message]
2007-01-24 21:13 ` Kai Großjohann
2007-01-23 8:07 ` Martin Jørgensen
2007-01-21 0:06 ` Adam Sjøgren
2007-01-20 12:33 ` Reiner Steib
2007-01-22 4:18 ` Gernot Hassenpflug
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=y68tzygtp71.fsf@department-of-alchemy.mit.edu \
--to=dmaze@mit.edu \
--cc=info-gnus-english@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.
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).