bren [mutt-users] <27/06/01 21:17 -0700>:
> Hoping that you might help me with a slight problem. I've got a .muttrc
> file that was working fine on my work machine. When I copied the .muttrc
> over to my home box, I can fire up mutt fine, and can even download
> messages from my POP account, but
On Wed, Sep 27, 2000 at 18:42:38 -0400, David T-G wrote:
> Yep, that was what I meant. Did you try a simple
>
> :set shell=/sbin/sh
>
> from within mutt? Did you try
>
> :set ?shell
>
> to see what mutt thinks $shell is holding?
The $shell variable is /only/ used for the shell-escape co
At 22:57 +0300 27 Sep 2000, Mikko Hänninen <[EMAIL PROTECTED]> wrote:
> For Sun, I don't know what the system call trace program is called --
> truss maybe, or was that some other OS? It may not have one
> (installed).
truss is correct. I'd probably use:
truss -o /tmp/mutt.truss -f -t exec m
On Wed, Sep 27, 2000 at 22:57:14 +0300, Mikko Hänninen wrote:
>
> I don't know the exact details (haven't looked at the source), but I
> would guess that the way Mutt starts an external program is with the
> system() sytem-function-call.
Mutt has its own implementaion of system() to have better
Marc --
...and then Marc van Dongen said...
% David T-G ([EMAIL PROTECTED]) wrote:
%
% : It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh,
% : which is guaranteed to be completely self-contained. If *that* works,
%
% I am assuming you are asking me to write a wrapper sc
Mikko Hänninen ([EMAIL PROTECTED]) wrote:
: OK.. And you can get a shell (via a terminal window), so you know the
: binary is executable etc.?
I am not exactly sure what you mean. External programs, like knews
can start vim as an external program to compose an email message.
[snip]
: Like
On Wed, Sep 27, 2000 at 10:57:14PM +0300, Mikko Hänninen wrote:
> I don't know the exact details (haven't looked at the source), but I
> would guess that the way Mutt starts an external program is with the
> system() sytem-function-call. If your Mutt can't run programs this
> way, then something
Marc van Dongen <[EMAIL PROTECTED]> wrote on Wed, 27 Sep 2000:
> Bruce DeVisser ([EMAIL PROTECTED]) wrote:
>
> : And what does :set ?shell return?
>
> shell="/usr/bin/bash"
>
> which is correct.
OK.. And you can get a shell (via a terminal window), so you know the
binary is executable etc.
David T-G ([EMAIL PROTECTED]) wrote:
: It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh,
: which is guaranteed to be completely self-contained. If *that* works,
I am assuming you are asking me to write a wrapper script around
mutt to set the shell. That didn't work.
Now
Morten Liebach ([EMAIL PROTECTED]) wrote:
[snip]
: This _is_ a long shot, but: what happens when you try to invoke vim from
: your shell?
It works great!
[snip]
Regards,
Marc van Dongen
Marc --
...and then Marc van Dongen said...
% Bruce DeVisser ([EMAIL PROTECTED]) wrote:
%
% : And what does :set ?shell return?
%
% shell="/usr/bin/bash"
%
% which is correct.
It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh,
which is guaranteed to be completely sel
On 27, Sep, 2000 at 01:36:46PM +0100, Marc van Dongen wrote:
> David T-G ([EMAIL PROTECTED]) wrote:
>
> [snip]
>
> : % : If you can't figure out what's up, try setting mutt's $editor to a
> : % : quickie script which calls vim and then waits for a keypress before
> : % : exiting so that you can
Bruce DeVisser ([EMAIL PROTECTED]) wrote:
: And what does :set ?shell return?
shell="/usr/bin/bash"
which is correct.
Regards,
Marc van Dongen
On Wed, Sep 27, 2000 at 04:09:04PM +0100, Marc van Dongen wrote:
> Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote:
>
> : Get out of both desktops into the sun shell... try mutt there.
>
> No success either:-(
And what does :set ?shell return?
--
- Bruce
Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote:
: Get out of both desktops into the sun shell... try mutt there.
No success either:-(
Regards,
Marc van Dongen
Marc van Dongen proclaimed on mutt-users that:
> Maybe this is an operating system related problem. I am using
> the CDE desktop at the moment but the problem also manifests
> itself if I use the openwindows desktop.
Get out of both desktops into the sun shell... try mutt there.
--
Suresh Ram
Mikko Hänninen ([EMAIL PROTECTED]) wrote:
[snip]
: > Good one. I hadn't thought of trying that. It fails
: > Other shell commands fail as well
[snip]
: I have no idea why you couldn't run any commands from within Mutt
: though, I've never heard of this kind of problem. Can you even
: st
Marc van Dongen <[EMAIL PROTECTED]> wrote on Wed, 27 Sep 2000:
> : !/path/to/your/editor/here
>
> Good one. I hadn't thought of trying that. It fails
> Other shell commands fail as well
Well, that's the "reason" then why your editor isn't getting called.
I have no idea why you couldn'
Mikko Hänninen ([EMAIL PROTECTED]) wrote:
: Marc van Dongen <[EMAIL PROTECTED]> wrote on Wed, 27 Sep 2000:
: > I changed the editor setting to a script that prints something,
: > reads a line and then starts to edit. It doesn't seem to be
: > called when I press `e.' I still get the `unmodified'
Marc van Dongen <[EMAIL PROTECTED]> wrote on Wed, 27 Sep 2000:
> I changed the editor setting to a script that prints something,
> reads a line and then starts to edit. It doesn't seem to be
> called when I press `e.' I still get the `unmodified' message.
What doesn't get called when you press e,
Marc --
...and then Marc van Dongen said...
% David T-G ([EMAIL PROTECTED]) wrote:
%
% [snip]
%
% : % : quickie script which calls vim and then waits for a keypress before
% : %
% : % I changed the editor setting to a script that prints something,
% : % reads a line and then starts to edit. It
David T-G ([EMAIL PROTECTED]) wrote:
[snip]
: % : If you can't figure out what's up, try setting mutt's $editor to a
: % : quickie script which calls vim and then waits for a keypress before
: % : exiting so that you can see any error messages that go by.
: %
: % I changed the editor setting to
Marc --
...and then Marc van Dongen said...
% David T-G ([EMAIL PROTECTED]) wrote:
%
% : % Aborted unmodified message.
% : %
% : % Any suggestions how to overcome this problem?
% :
% : You might start by checking your $editor setting in your muttrc and your
%
% My editor setting points to an
Marc van Dongen proclaimed on mutt-users that:
> That's not the problem. Mutt doesn't seem to let me edit
> at all. With this setting, I can postpone a message for
> later, then recall it and use `e` to edit but mutt won't
> let me
Then check if your tmpdir directory is set properly, or is
David T-G ([EMAIL PROTECTED]) wrote:
: % mutt does not allow me to write a message.
: % Istead it displays a
: % Aborted unmodified message.
: % message.
: %
: % Any suggestions how to overcome this problem?
:
: You might start by checking your $editor setting in your muttrc and your
My edito
David Champion ([EMAIL PROTECTED]) wrote:
: > I just re-installed vim on my system.
: > When I now try to compose a message
: > after I enter the name of the recipient
: > mutt does not allow me to write a message.
: > Istead it displays a
: > Aborted unmodified message.
: > message.
:
: set a
Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote:
: I rather suspect that the path to vim is wrong in his .muttrc
: Especially if he had an rpm install which would dump vim in /bin or /usr/bin -
: and then compiled a new vim from a tarball, that'd put it into /usr/local/bin
:
: Use `which vim` t
Marc --
...and then Marc van Dongen said...
% Hi there,
%
% I just re-installed vim on my system.
...
% mutt does not allow me to write a message.
% Istead it displays a
% Aborted unmodified message.
% message.
%
% Any suggestions how to overcome this problem?
Fix your vim configuration :-)
David Champion proclaimed on mutt-users that:
> On 2000.09.26, in <[EMAIL PROTECTED]>,
> "Marc van Dongen" <[EMAIL PROTECTED]> wrote:
> > Hi there,
> > after I enter the name of the recipient
> > mutt does not allow me to write a message.
> > Istead it displays a
> > Aborted unmodifie
On 2000.09.26, in <[EMAIL PROTECTED]>,
"Marc van Dongen" <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I just re-installed vim on my system.
> When I now try to compose a message
> after I enter the name of the recipient
> mutt does not allow me to write a message.
> Istead it displays a
>
User Jasapp proclaimed on mutt-users that:
>First, I hit "m", for new mail, then type in the address on the "to:"
>line, and hit enter. Then it just says,
>"Aborted unmodified message.". I can send mail using other muas just
>fine, and I've checked all ther permissions. Can someone help me out?
User Jasapp <[EMAIL PROTECTED]> wrote on Wed, 05 Jul 2000:
> First, I hit "m", for new mail, then type in the address on the "to:"
> line, and hit enter. Then it just says,
> "Aborted unmodified message.".
Sounds like the execution of your editor fails. That is, after Mutt
has created a template
32 matches
Mail list logo
