Bug 103396
Summary: | mutt fails to launch editor | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Everett Lipman <redhat> |
Component: | mutt | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-08-29 21:26:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Everett Lipman
2003-08-29 18:41:42 UTC
Can you attach your .muttrc? Created attachment 94077 file names have been changed Comment on attachment 94077 set folder=~/somedir set record=~/somedir/somefile set postponed=~/somedir/anotherfile set sendmail=/home/user/myscript set ispell="/usr/bin/aspell --mode=email check" set index_format="%4C %Z %{%d%b%y %H:%M:%S %Z} %-15.15L (%4l) %s" set sort=mailbox-order set simple_search="~B %s" set pager_context=1 set print_command="enscript -T3" set edit_headers autoedit fast_reply menu_scroll postpone unset editor user_agent use_from move abort_nosubject confirmappend include bind pager N search-opposite bind pager b previous-page bind index b previous-page bind index G last-entry bind index 0 first-entry bind index N search-opposite bind attach r exit exec last-entry ignore received content- mime-version message-id return-path status ignore in-reply-to references list- lines color hdrdefault red default color quoted brightblue default color signature red default color indicator brightyellow red color error brightred default color status yellow blue color tree magenta default # the thread tree in the index menu color tilde magenta default color message brightcyan default color markers brightcyan default color attachment brightmagenta default color search default green # how to hilite search patterns in the pager color header cyan default ^(From|Subject): color body magenta default "(ftp|http)://[^ ]+" # point out URLs color body magenta default [-a-z_0-9.]+@[-a-z_0-9.]+ # e-mail addresses color underline brightgreen default OK, I'm missing something obvious... without having sendmail point at the nonexistent script referenced above, I don't even get to the edit menu. Detailed description of what I do: 1. mutt -nz address I am prompted for a subject, I type "foo" and hit <Enter>. 2. Type a line of text and again hit <Enter>. 3. Type "." 4. Type <Enter> At this point I am in the menu screen, and if I type "y", the message will be sent. 5. Type "e" Screen flashes, and it is at this point that the execve() is attempted and the following error sh: line 1: /tmp/mutt-elo-25292-1: Permission denied is generated because the "vi" is left out of the execve() command string. All of this happens before the message is ever sent, so I don't think the fact that I use a funny script as my sendmail should have any effect. I used an identical setup under mutt 1.4i and never had this problem. BTW, in my environment, EDITOR=vi VISUAL=vi From the muttrc man page: editor Type: path Default: "" This variable specifies which editor is used by mutt. It defaults to the value of the VISUAL, or EDITOR, environment variable, or to the string "vi" if neither of those are set. The problem still occurs if EDITOR and VISUAL are unset. Ah, you said mailx mode before, which implies -x, which does not prompt. This is a general consequence of 'unset editor'. This unsets any value of editor, including the default inherited ones. Sorry for the confusion about mailx mode; I did not specify -x on the command line, but the "unset editor" command results in mutt starting in mailx mode with the important difference that the "." does not send the message, but rather puts you in the mutt menu where you can attach files if you wish. As far as whether or not this is a bug, I have a few comments: 1) I don't know of another way to have a default behavior that doesn't require an editor and still allows attachments. 2) This configuration worked flawlessly under version 1.4. 3) I still think it is a bug for mutt to try to have sh execute the temporary file holding the email message. The old behavior was more rational, and the new behavior could have unpleasant consequences. If the present version is doing what was intended, it should give an error message such as "No editor specified" rather than calling execve() with the message as the argument. |