On Thu, May 08, 2014 at 06:37:21PM -0400, Guy Gold wrote:
> The reason I'm using the !cat option is - like you mentioned, if
> I only use ":r /tmp/file", then, things get 'messed' up. And, while
> in mutt, I find out that I'm editing two files, not good..
Mostly I reply here due to a curiosity: W
On Fri,May 09 04:24:PM, Jean-Rene David wrote:
>
> Not at all. Did you try it?
>
> You would have two files to edit if you did:
>
> vim -c ":e /path/to/file"
>
> or
>
> vim /path/to/file
>
> But not with:
>
> vim -c ":r /path/to/file"
>
I did try it, and arrived to the !cat idea for that r
On Fri, May 09, 2014 at 03:14:03PM -0700, Shawn Zaidermann wrote:
> Is there a way to completely disable the shell-escape feature?
In short, no. If you're trying to prevent mutt users from gaining any
access to the shell, you also have to concern yourself with things
like:
my_var=`run arbitrar
On 09.05.14 09:55, David Champion wrote:
> You can unbind the key (or bind it to no-op), but the user can still
> rebind it unless you also remove the enter-command binding (preventing
> them from entering a bind command). Also ensure that they cannot source
> any muttrc files (check bindings for
