* Richard Cobbe ([EMAIL PROTECTED]) [020516 18:05]:
> Lo, on Thursday, May 16, Cam Ellison did write:
> > set editor="emacs '+/^$' \"set textwidth=70\""
> I'm not entirely sure what the '+/^$' means---is this perhaps a Mutt
> thing?
No, it's a vim thing.
> The `set textwidth=70' is almost certai
> On Thu, 16 May 2002, "cam" == Cam Ellison wrote:
cam> set editor="emacs '+/^$' \"set textwidth=70\""
Nope. On my system this tells emacs to edit a file named (something like)
"textwidth=70". Look at your list of buffers when you use this command string.
cam> What should I do differen
On Thu, May 16, 2002 at 07:10:30PM -0700, Cam Ellison wrote:
> Thank you, Richard. I don't know about the '+/^$' bit either - I
> cribbed my .muttrc from someone else, and dutifully copied that bit.
Looks like both that and the textwidth setting came from a vim user.
'+/^$' will tell vim to go to
Similar advice from two of you -- Alan and yourself. I have tried
your route, and I see that is is finally wrapping as I write. This is
a great relief.
Thank you, all, very much.
Now, I just need to straighten out my problems with a couple of
service providers.
Thanks again
Cam
* Bob Bernst
> On Thu, 16 May 2002, "cam" == Cam Ellison wrote:
cam> set editor="emacs '+/^$' \"set textwidth=70\""
Nope. On my system this tells emacs to edit a file named (something like)
"textwidth=70". Look at your list of buffers when you use this command string.
cam> What should I do differen
On 0, Cam Ellison <[EMAIL PROTECTED]> wrote:
> I hate replying to my own posts, but I see that it did not work. But then, I
> forgot to restart mutt, which wasn't very clever. Sorry to take the
> bandwidth, but I need to test this so I can quit annoying everyone.
Evidently not. Since you see
Cam Ellison <[EMAIL PROTECTED]> writes:
> set editor="emacs '+/^$' \"set textwidth=70\""
Put this in your .emacs:
(setq default-major-mode 'text-mode)
(add-hook 'text-mode-hook 'turn-on-auto-fill)
--
Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors!
Tact is the art of making a point w
I hate replying to my own posts, but I see that it did not work. But then, I
forgot to restart mutt, which wasn't very clever. Sorry to take the bandwidth,
but I need to test this so I can quit annoying everyone.
* Cam Ellison ([EMAIL PROTECTED]) wrote:
> Thank you, Richard. I don't know abo
Thank you, Richard. I don't know about the '+/^$' bit either - I cribbed my
.muttrc from someone else, and dutifully copied that bit.
So I have followed your advice, andmade the changes. I had not set up xemacs,
and of course it has done its own thing, so we shall see the results now. I am
d
Lo, on Thursday, May 16, Cam Ellison did write:
> * Gary Hennigan ([EMAIL PROTECTED]) wrote:
>
> >
> > And, *please*, for the love of God and country, can you wrap your
> > lines at 70 characters or so?!
> >
>
> I would love to, but every attempt seems to go nowhere. Not everyone
> complains,
* Gary Hennigan ([EMAIL PROTECTED]) wrote:
>
> And, *please*, for the love of God and country, can you wrap your
> lines at 70 characters or so?!
>
I would love to, but every attempt seems to go nowhere. Not everyone
complains,
but I see the litle red markers coming back indicating that mutt
11 matches
Mail list logo
