Re: Mutt/Neomutt and mailcap

2021-09-18 Thread David Wright
On Thu 16 Sep 2021 at 05:37:43 (-0500), Nate Bargmann wrote: > * On 2021 15 Sep 21:36 -0500, David Wright wrote: > > I think what your system is doing is as follows: > > > > You probably have in your (default) /etc/Muttrc: > > In my case, /etc/neomuttrc, and the following does exist. > > My assu

Re: Mutt/Neomutt and mailcap

2021-09-17 Thread Jonathan Dowland
On Thu, Sep 16, 2021 at 07:43:25AM -0400, Greg Wooledge wrote: Unfortunately, it breaks in Bourne-family shells. snip In Bourne/POSIX/bash, semicolon is a command terminator or separator, and may not appear by itself, or at the start of a command. It may appear at the end. Good catch! I neve

Re: Mutt/Neomutt and mailcap

2021-09-16 Thread Greg Wooledge
On Thu, Sep 16, 2021 at 08:47:32AM +0100, Jonathan Dowland wrote: > On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote: > > I don't know why there's a ";" in front of it. > > That's (part of) my shell prompt. It's a convention originating in the > rc shell (although I learned of it from

Re: Mutt/Neomutt and mailcap

2021-09-16 Thread Nate Bargmann
* On 2021 15 Sep 21:36 -0500, David Wright wrote: > I think what your system is doing is as follows: > > You probably have in your (default) /etc/Muttrc: In my case, /etc/neomuttrc, and the following does exist. My assumptions have been that the system RC is ignored when a user's RC exist. I am

Re: Mutt/Neomutt and mailcap

2021-09-16 Thread Nate Bargmann
* On 2021 16 Sep 02:35 -0500, Andrei POPESCU wrote: > For neomutt in buster I have this in .neomuttrc: > > # neomutt disabled viewing text/* as text (except text/plain) > # re-enable common file types received (requires corresponding .mailcap entry) > auto_view text/x-diff > auto_view text/x-patch

Re: Mutt/Neomutt and mailcap

2021-09-16 Thread tomas
On Thu, Sep 16, 2021 at 08:47:32AM +0100, Jonathan Dowland wrote: > On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote: [...] > >I don't know why there's a ";" in front of it. > > That's (part of) my shell prompt [...] aaah :-) Thanks for clearing that up. My hunch was at least

Re: Mutt/Neomutt and mailcap

2021-09-16 Thread Jonathan Dowland
On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote: Jonathan's message confused me too. As far as I can tell, "see" is a *shell* command, not a mutt command. Sorry for the confusion, I should have been clearer that it was a shell command, intended to narrow the problem down to eithe

Re: Mutt/Neomutt and mailcap

2021-09-16 Thread Andrei POPESCU
On Mi, 15 sep 21, 08:37:51, Nate Bargmann wrote: > As there are a lot of Mutt/Neomutt users on this list, maybe someone can > point me in the right direction. > > Recently via another mailing list a message was posted that included a > diff file with the extension of .patch. The MIME encoding is

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread tomas
On Wed, Sep 15, 2021 at 09:34:50PM -0500, David Wright wrote: [...] > BTW, your shell command, > > !see --norun application/octet-stream:/dev/null > > will give you an answer in the context of a subshell, and > not necessarily in the context of mutt itself [...] Definitely, that's another po

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread David Wright
On Wed 15 Sep 2021 at 16:21:12 (-0500), Nate Bargmann wrote: > * On 2021 15 Sep 14:20 -0500, to...@tuxteam.de wrote: > > On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote: > > > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote: > > > > * On 2021 15 Sep 10:44 -0500, Jonathan

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread Nate Bargmann
* On 2021 15 Sep 14:20 -0500, to...@tuxteam.de wrote: > On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote: > > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote: > > > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote: > > > > What does this command report? > > > > > > >

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread tomas
On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote: > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote: > > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote: > > > What does this command report? > > > > > > ;see --norun application/octet-stream:/dev/null > Jonathan

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread Nate Bargmann
* On 2021 15 Sep 13:02 -0500, Greg Wooledge wrote: > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote: > > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote: > > > What does this command report? > > > > > > ;see --norun application/octet-stream:/dev/null > > > > In the message

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread Greg Wooledge
On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote: > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote: > > What does this command report? > > > > ;see --norun application/octet-stream:/dev/null > > In the message window, "key not bound", in the view attachment window, > "no ta

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread Nate Bargmann
* On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote: > On Wed, Sep 15, 2021 at 08:37:51AM -0500, Nate Bargmann wrote: > > application/octet-stream; vim %s; description=Patch file; > > nametemplate=%s.patch > > application/octet-stream is a fairly generic mime type (and an odd > choice for a text

Re: Mutt/Neomutt and mailcap

2021-09-15 Thread Jonathan Dowland
On Wed, Sep 15, 2021 at 08:37:51AM -0500, Nate Bargmann wrote: application/octet-stream; vim %s; description=Patch file; nametemplate=%s.patch application/octet-stream is a fairly generic mime type (and an odd choice for a text file, but so it goes). You may find vim is not a suitable tool for