Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

pasting content problems using VIM + MUTT

31 views
Skip to first unread message

Joey Stanford

unread,
Feb 23, 2013, 12:14:03 PM2/23/13
to
Howdy,

I'm new to mutt so thanks in advance for the replies.

When I post text content into VIM (normally) it pastes correctly
including lines with longer than 78 characters.

When I create a new mail in mutt and VIM opens, I have issues. When I
paste the same content it's wrapped to 78 and is prefixed by an
asterisk (which then triggers the vim indent plugin).

How do I fix this? I'm using the vimrc_example as my .vimrc and for
mutt I'm not passing an editor line, it just correctly goes to vim.
I've tried about 10 variations of editor = vim with options to turn off
wrap, reset tw, etc. with no luck.

Thanks,

Joey

Message has been deleted

Heikki Kallasjoki

unread,
Feb 25, 2013, 5:23:40 AM2/25/13
to
On 2013-02-23, Joey Stanford <jo...@stan4d.net> wrote:
> When I post text content into VIM (normally) it pastes correctly
> including lines with longer than 78 characters.
>
> When I create a new mail in mutt and VIM opens, I have issues. When I
> paste the same content it's wrapped to 78 and is prefixed by an
> asterisk (which then triggers the vim indent plugin).

I have no idea where the asterisk might come from, but the text width
setting is presumably due to filetype.vim, which detects email messages
of various clients based on the file name.

As for disabling it, making a .vimrc.mutt with "filetype off" (instead
of the standard "filetype plugin indent on") and specifying that to vim
with the -u option should work.

(Though for me a simple ":set tw=0" when pasting also works, and
suffices.)

--
Heikki Kalolasjoki

Joey Stanford

unread,
Feb 25, 2013, 7:10:18 PM2/25/13
to
On 2013-02-23 19:26:43 +0000, Roger Burton West said:
> Certainly sounds as though vim's starting up in some unexpected
> mode. ps -fwwwC vim (when you've got mutt+vim open in another window)
> to find out what the command-line arguments are? Might be a starting
> point.

Good idea. Sadly it didn't reveal anything other than it was using the
same command I have it mutt (set spell) I test the command from the
terminal and via mutt and pasting while called from mutt still has the
weird issue.

Joey Stanford

unread,
Feb 26, 2013, 4:50:49 PM2/26/13
to
On 2013-02-25 10:23:40 +0000, Heikki Kallasjoki said:
> As for disabling it, making a .vimrc.mutt with "filetype off" (instead
> of the standard "filetype plugin indent on") and specifying that to vim
> with the -u option should work.
>


That's worth a try. I did find a workaround though, :set paste


Eike Rathke

unread,
Mar 2, 2013, 1:53:03 PM3/2/13
to
* Joey Stanford, 2013-02-26 21:50 UTC:
> That's worth a try. I did find a workaround though, :set paste

That is not a workaround, it is the proper cure if you don't want to
take various effects place when _pasting_.

Eike

--
PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication.
New key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Old key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
Support the FSFE, care about Free Software! https://fsfe.org/support/?erack
0 new messages