From: Lurkos <lurkos.usenet@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] IMAP, labels, editors
Date: Sun, 28 Nov 2010 00:34:55 +0100 [thread overview]
Message-ID: <AANLkTinMxU2J=t4LP=Tp-d-BeXVaQ1kNc2yGXOzgorpx@mail.gmail.com> (raw)
In-Reply-To: <1290890855-sup-3282@niflheimr>
On Sat, Nov 27, 2010 at 9:57 PM, Moritz Wilhelmy <moritz+sup@wzff.de> wrote:
>>> I've read in the latest History file that IMAP support is deprecated.
>>> Are you going to drop it? I mainly use IMAP to read my e-mail boxes,
>>> because I need to deal with them from different workstations (say:
>>> home, office, laptop, etc.).
>>> For this reason the local Maildir approach won't work for me.
>>
>> You can use offlineimap to fetch e-mails from your IMAP server and
>> save them as Maildir that are then added in sup. By setting your hooks
>> properly you can automatically call offlineimap before polling (see
>> the wiki).
>
> Alternatives to offlineimap to store mail in mbox/maildir include getmail
> (which is what I use) and fetchmail.
The main drawback of this approach is that you have to copy all your
mailbox in every location.
This mean several GiB for me.
That's why I would prefer to keep everything on the IMAP server (and
periodically backup it in a single computer).
>>> About message composition, do you have any recommended editor, given
>>> the fact that I never used a lot Vi nor Emacs?
>>
>> I use emacs with post-mode.
>
> sup's keybindings are modeled largely after mutt's, and not really modeled
> after neither vim nor emacs, so you don't have any benefits in learning
> how to use sup if you already know how to use vim/emacs (or vice versa).
> sup has a setting where you can change your preferred editor. As far as I
> remember, the tool that initially writes the configuration (`sup-config')
> defaults to vim.
> Personally, I use vim with mail-syntax-hilighting.
That's true: *sup* initially selects vim as default mail editor.
I never had before special requirements for text editor and therefore
gedit was enough.
Do you think is worth spending time to learn a text-based editor even
for writing e-mails?
Cheers,
--
Lurkos
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-11-28 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 18:17 Lurkos
2010-11-27 20:26 ` Damien Leone
2010-11-27 20:57 ` Moritz Wilhelmy
2010-11-27 23:34 ` Lurkos [this message]
2010-11-28 1:27 ` Lurkos
2010-11-28 9:21 ` Damien Leone
2010-11-28 14:05 ` Lurkos
2010-11-28 14:50 ` Damien Leone
2010-11-29 18:59 ` Lurkos
2010-11-29 20:08 ` Damien Leone
2010-11-30 2:36 ` Lurkos
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='AANLkTinMxU2J=t4LP=Tp-d-BeXVaQ1kNc2yGXOzgorpx@mail.gmail.com' \
--to=lurkos.usenet@gmail.com \
--cc=sup-talk@rubyforge.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