#3651: vanishing input wrt entry of folders with spaces in names
----------------------------+----------------------
 Reporter:  balderdash      |      Owner:  mutt-dev
     Type:  defect          |     Status:  new
 Priority:  major           |  Milestone:
Component:  user interface  |    Version:  1.5.21
 Keywords:                  |
----------------------------+----------------------
 The following bug affects all versions of OS X from 10.4.11 through
 10.8.5, including PPC versions up through the last one (10.5.8).  I am on
 the latest tip of mutt from the hg repo.  This bug has been around for at
 least a year.

 Mutt is buggy wrt imap folder names that have spaces in them.  In
 particular, here is what happens with an imap Gmail account.  On Gmail,
 the location of all "sent mail" is:
 {{{
    =[Gmail]/Sent Mail
 }}}
 However, if in mutt I do the following keystrokes to view the contents of
 that folder:
 {{{
    c=[Gmail]/Sent<space>
 }}}

 then immediately the text-entry prompt is *cleared*.  As soon as the space
 key is hit, everything I had typed vanishes, though mutt remains in the
 prompt waiting for me to enter a folder name.

 It doesn't matter whether you escape the space first with a backslash, or
 include the whole thing in quotes.

 This makes it impossible to go straight to that folder.  One must do "c?"
 and navigate.

 As far as I can see, this is a totally general problem.  It doesn't need
 to be a gmail account, and it doesn't have to be a request to view an imap
 folder.  Mutt destroys what I've entered even if I look for a local folder
 with a space in the name.

 Now, I normally NEVER put spaces in the names of my folders, but in the
 case of Gmail I have no choice.  So this bug could be really old, because
 I haven't used Gmail for very long.

 Also, I discovered that one can do:
 {{{
   c=[Gmail]/Se<tab>
 }}}

 and mutt will autocomplete the relevant text.  So there is a workaround.
 But it is still a bug.

 Note that this behavior occurs on both Terminal.app and iTerm.app, and it
 doesn't matter whether the emulation is set to xterm-color or xterm-
 256color.  Also I have ruled out my local muttrc and friends as the
 culprit, by moving them out of the way and noting the problem with a fresh
 mutt.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3651>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to