message width in vim?
I *know* I saw how to do this recently on a mailing list but I couldn't find it. I need to know how to set the message width when using vim as my editor. I didn't see anything helpful in the vim docs for this, but I might have missed something. (Not much traffic on this list lately it seems) -- -- Chris Gushue -- [EMAIL PROTECTED] -- GCS d- s+:- a23 C++>$ UL+++ P+>++ L+++ E W++ N++ o-- K- w--- O- M-- V- PS+++ PE Y+ PGP++ t++ 5+ X++ R- tv+ b++ DI+ D+ G++ e h! r y+ -- http://seymour.napalm.net --- http://owirc.napalm.net -- PGP signature
Re: message width in vim?
On Sun, Aug 29, 1999 at 03:59:15PM -0230, Chris Gushue wrote: > I *know* I saw how to do this recently on a mailing list but I couldn't > find it. I need to know how to set the message width when using vim as > my editor. I didn't see anything helpful in the vim docs for this, but > I might have missed something. > Many ways to do this probably. One easy way is start vim: set editor="vim +'set tw=xx'" in .muttrc. -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: message width in vim?
I have this in my /etc/vimrc: autocmd BufRead mutt* set textwidth=72 autoindent Hope this is what you want... Chris Gushue [[EMAIL PROTECTED]] wrote: > I *know* I saw how to do this recently on a mailing list but I couldn't > find it. I need to know how to set the message width when using vim as > my editor. I didn't see anything helpful in the vim docs for this, but > I might have missed something. > > (Not much traffic on this list lately it seems) > > -- > -- Chris Gushue -- [EMAIL PROTECTED] -- > GCS d- s+:- a23 C++>$ UL+++ P+>++ L+++ E W++ N++ o-- K- w--- O- > M-- V- PS+++ PE Y+ PGP++ t++ 5+ X++ R- tv+ b++ DI+ D+ G++ e h! r y+ > -- http://seymour.napalm.net --- http://owirc.napalm.net -- -- Shao Zhang - Running Debian 2.1 ___ _ _ Department of Communications/ __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: [EMAIL PROTECTED] |___/ _
Re: IMAP folder path
On Saturday, 28 August 1999 at 01:10, Brian D. Winters wrote:
> On Fri, Aug 27, 1999 at 05:46:46PM -0500, David DeSimone wrote:
> > Brian D. Winters <[EMAIL PROTECTED]> wrote:
> > >
> > > set spoolfile='{imapserver}inbox'
> > > set folder='{imapserver}INBOX'
> >
> [lots of explanation from David as to why this doesn't make sense omitted]
[snip]
> * There doesn't seem to be any way to create a directory hierarchy, at
> least not under mutt. Hard coding "INBOX." may be their answer to
> the {server}/folder problem you mentioned, or it may just be
> completely arbitrary. ("INBOX/" appears to be equivalent to
> "INBOX.", either through magic on the server or magic in pine.)
I'm working on it. Mutt should let you do this since in cases like this one
there's no other way (well, except for using a different IMAP client).
INBOX/ vs INBOX. should be handled by Mutt, which should be able to figure
out which delimiter is used on the server and translate '/' to it.
> * With my friend's server, using the folder browsing features in the
> devel branch to browse = shows two lines for every folder. One line
> is "=foldername", and the other line is "=foldername.". (This is
> from memory, so the exact text leading up to "foldername" and
> "foldername." may be more complicated.) It is the non-'.' folder
> which contains actual e-mail. Attempting to change to the folder
> ending in '.' results in nothing happening (I don't remember seeing
> any error messages from mutt even, although it has been a couple
> weeks so I may be mistaken). I have no idea what the '.' folder is
> for.
This is ugly I agree, but I'm not sure how to solve it. The intended
behaviour is that the folder without the '.' contains your mail (as you
have found), but the one with the trailing . is there so you can enter it
searching for subfolders. On UW IMAP servers folders either have mail or
subfolders, but it seems on Cyrus they can have both. If selecting the
folder with the trailing '.' results in nothing happening, that is a bug. I
haven't tested against Cyrus or against any folders that use anything other
than '/' as a delimiter, so it wouldn't be surprising. I would love to see
the .muttdebug0 file from 'mutt -d4' for a session where you switch to one
of these folders. Also I'm going to set up a Cyrus IMAP server somewhere
around here so I can do some limited testing against it.
--
Brendan Cully <[EMAIL PROTECTED]> | OLD SKOOL ROOLZ
"I hope I don't win| .-_|\
The rules say to bring a friend | / \
I don't have any" | Perth ->*.--._/
Re: IMAP folder path
On Friday, 27 August 1999 at 17:46, David DeSimone wrote:
[snip]
> But, as shown, a folder name such as "+folder" would expand out to be
> "{imapserver}INBOX/folder". That's clearly the wrong path; it should be
> "{imapserver}folder" to reference a folder stored in your home
> directory.
>
> But Mutt insists on inserting that slash character, so a setting of
> simple "{imapserver}" for $folder would expand to "{imapserver}/folder",
> which refers to a file in the root directory, and not the user's home
> directory.
Okay, that's a bug. I'll try to get that one fixed soon. Should mutt append
the delimiter except against the root namespace {imapserver}, or should you
just have to say 'set folder="{imapserver}Mail/" (mutt will never append
the slash to imap folders)?
> On my server, I have login access, and so I have placed all
> my folders in a subdirectory called "mail". So, I can set
> folder="{imapserver}mail", and thus Mutt will expand "+folder"
> to be "{imapserver}mail/folder", which is correct.
>
> Well.. it's correct, if your server uses "/" as a pathname separator.
> If it only understands ".", the above wouldn't work...
It should work. Mutt should translate '/' to the delimiter appropriate to
the path. If it doesn't I'd like to see it (I haven't tested this code, just
read it).
--
Brendan Cully <[EMAIL PROTECTED]> | OLD SKOOL ROOLZ
"I hope I don't win| .-_|\
The rules say to bring a friend | / \
I don't have any" | Perth ->*.--._/
