ports/63192: mutt change breaks vim syntax highlighting

Dan Foster dsf at globalcrossing.net
Sat Feb 21 22:20:12 UTC 2004


>Number:         63192
>Category:       ports
>Synopsis:       mutt change breaks vim syntax highlighting
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat Feb 21 14:20:11 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     Dan Foster
>Release:        FreeBSD 4.9-RELEASE-p2 i386
>Organization:
New York Web Works
>Environment:
System: FreeBSD mail1.nywebworks.com 4.9-RELEASE-p2 FreeBSD 4.9-RELEASE-p2 #9: Mon Feb 9 00:01:13 EST 2004 root at mail1.nywebworks.com:/usr/src/sys/compile/MAIL1 i386


	1 GHz Intel Pentium III (Coppermine), FreeBSD 4.9-RELEASE
>Description:
	The default builds of mutt no longer creates temporary files in the format of mutt-<short hostname>-<pid>-<revision number>. The current temporary file naming is apparently mutt-<short hostname>-<8 chars random string>. 
	
	This breaks syntax highlighting if your editor is vim because vim no longer enables syntax highlighting for mutt mail messages due to the change in the mutt temporary file naming. A fix is provided.

	While mutt is the culprit, the fix is trivial and should be done by the vim ports maintainer since this is really specific to vim, and not mutt -- mutt can interoperate with any number of editors; but this one is a vim-specific issue even though it is mutt that changed the naming.
>How-To-Repeat:
	Using SecureCRT (or equivalent ssh client), I have vt100 emulation and ANSI coloring enabled. My ~/.login (tcsh shell) has 'set term=xterm'. My ~/.vimrc file has 'syntax enable'. Both mutt and vim were from ports, default build options.

	Run latest mutt from ports, and reply to any mail message. It will fail to apply syntax highlighting to the mail message header lines.

	Reproduced after original informal problem report from another user.
>Fix:

	patch /usr/local/share/vim/vim62/filetype.vim and add an additional check to the line that has an au(tocommand) matching mutt-*-\d\+.
	
	To this line, add a new check:

	mutt-*-\w\{8\}

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list