From: harven <harven@free.fr>
To: info-gnus-english@gnu.org
Subject: Re: gnus and pine
Date: Fri, 19 Dec 2008 12:38:59 +0100 [thread overview]
Message-ID: <m2zlis5r8s.fsf@free.fr> (raw)
In-Reply-To: <mailman.3109.1229682307.26697.info-gnus-english@gnu.org>
Frédéric Perrin <frederic.perrin@resel.fr> writes:
> Le Jeudi 18 à 22:55, harven a écrit :
>> Xavier Maillard <xma@gnu.org> writes:
>>> harven <harven@free.fr> writes:
>>>> I recently switched from Pine to Gnus as a mail reader.
>>>> I wrote a quick tutorial on the emacs wiki to make Gnus behave a
>>>> little more like Pine :
>>>> http://www.emacswiki.org/emacs-en/GnusAndPine
>>>
>>> I am wondering why you made the switch.
>>
>> I have used Pine for some years now, and it was nice, albeit for the
>> fact that Pine has a built-in editor which is pretty limited when it
>> comes to localisation, formatting, completion and else. So I began to
>> use emacs as an external editor. After a while, it felt a bit strange
>> to spawn big emacs from little pine, when often there was already some
>> emacs instance hanging around. So I started looking for another way to
>> check my mail. Gnus is pine-compatible, that is, it can read and write
>> in the pine mailbox, and it is provided with emacs, so I gave it a
>> try.
>
> I guess the question was « why do you use $foo when you want $bar's
> behaviour ? ». Also, have you looked at emacsclient ? It enables you to
> reuse a existing emacs, spawning it in a new buffer.
Then I guess the answer is « I decided to use $foo instead of $bar + $foo
because $foo can do whatever $bar can do, after some customization »
next prev parent reply other threads:[~2008-12-19 11:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 10:44 harven
2008-12-18 6:33 ` Xavier Maillard
[not found] ` <mailman.3044.1229622406.26697.info-gnus-english@gnu.org>
2008-12-18 21:55 ` harven
2008-12-19 10:24 ` Frédéric Perrin
[not found] ` <mailman.3109.1229682307.26697.info-gnus-english@gnu.org>
2008-12-19 11:38 ` harven [this message]
2008-12-19 21:43 ` Xavier Maillard
[not found] ` <mailman.3140.1229723201.26697.info-gnus-english@gnu.org>
2008-12-20 0:25 ` David Kastrup
2008-12-20 10:53 ` harven
2008-12-22 6:26 ` Xavier Maillard
2008-12-22 9:21 ` Sivaram Neelakantan
2008-12-22 10:31 ` Xavier Maillard
2008-12-22 11:41 ` Reiner Steib
[not found] ` <mailman.3228.1229928365.26697.info-gnus-english@gnu.org>
2008-12-22 11:25 ` Richard Riley
2008-12-22 13:50 ` Xavier Maillard
[not found] ` <mailman.3241.1229957171.26697.info-gnus-english@gnu.org>
2008-12-22 15:27 ` Richard Riley
2008-12-22 16:22 ` harven
2008-12-22 16:27 ` Richard Riley
2008-12-22 17:14 ` harven
2009-01-04 0:54 ` Joe Fineman
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=m2zlis5r8s.fsf@free.fr \
--to=harven@free.fr \
--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).