#838992 mutt: using mutt, will not default to home mail directory: "c", "?" with "set folder" remains in /var/mail

Package:
mutt
Source:
mutt
Description:
text-based mailreader supporting MIME, GPG, PGP and threading
Submitter:
jackson
Date:
2022-06-13 07:45:13 UTC
Severity:
normal
Tags:
#838992#5
Date:
2016-09-27 13:56:38 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
     Upgrading from older version
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     No change, as of yet, in config file ameliorates this behavior
   * What was the outcome of this action?
    No change
   * What outcome did you expect instead?
     "set folder" has changed

*** End of the template - remove these template lines ***

#838992#10
Date:
2016-10-01 05:30:32 UTC
From:
To:
Control: tag -1 +moreinfo
a) What directory do you expect instead?
b) where is directory that you expect, set in .muttrc?

#838992#17
Date:
2016-10-02 16:32:39 UTC
From:
To:
Hi Antonio,

Let me reply in behalf of jackson for

a) What directory do you expect instead?
the one set by 'set folder' in .muttrc

b) where is directory that you expect, set in .muttrc?
see a

I am not sure if this behavior was on purpose, but it used to work and be convenient.

For instance, see the difference between mutt <=1.6 & 1.7 when:
.muttrc contains 'set folder=~/my/mail/mailboxes'
~/my/mail/mailboxes contains following mailboxes
   mybox1 mybox2 ...
key 'c' is binded to change-folder (default)

[in mutt 1.6 or earlier]
pressing keys 'c' '?' open folder ~/my/mail/mailboxes
then it list mybox1 mybox2 ...
then it is very convenient to open those mailboxes: just move the cursor on 1 of them and press enter.

[from mutt 1.7]
pressing keys 'c' '?' open folder /var/mail
then one need to select with the cursor
..
..
home
myaccount
my
mail
mailboxes
then it list mybox1 mybox2 ...

Needless to say that this it much less convenient.

BR, Franck

#838992#22
Date:
2016-10-04 22:37:39 UTC
From:
To:
I'll also give my input on what changed in the folder navigation in
Mutt recently.

This particular change happened between 1.7.0-2 and 1.7.0-3, I'm not
sure if it also applies to the problems the other uses have reported:

$ mkdir -p ~/Mail/INBOX/{cur,new,tmp}
$ echo 'set spoolfile=~/Mail/INBOX/' > .muttrc

Now open mutt and press 'c' followed by '?' to list the mailboxes.

1) In previous versions of Mutt you'd see what's under ~/Mail (the
   'INBOX' directory in this case). If you select INBOX then it would
   go to the index view and open the INBOX maildir (which is empty).

   In Mutt >= 1.7.0-3 you see what's under ~/Mail/INBOX/ (that is, the
   cur, new and tmp directories internal to the maildir format). But
   you cannot do anything with those, you need to navigate to the
   parent directory and from there open INBOX.

   This is annoying but it can be fixed by removing the trailing '/'
   from the 'spoolfile' line in the .muttrc file. Still, it took me
   a while to realize that and it's very irritating when changing
   folders, so it would be nice to have it fixed in the package.

2) From the folder view, navigate to the parent directory over and over
   until you reach the root directory.

   In older versions of Mutt you simply press Enter all the time
   because '..' is highlighted by default when you change directories.

   In Mutt >= 1.7.0-3 when you move to the parent directory the cursor
   does not highlight '..', but rather the directory where you are
   coming from.

   I'm hesitant to consider this a bug, but it's certainly a change
   of behavior that is very noticeable to regular Mutt users. I'm not
   sure what the use case is, but when you want to attach a file and
   you need to browse the directory tree in order to open it I find
   the old behavior more convenient. I sometimes have to use different
   versions of Mutt in different machines so that makes things worse.

I guess these issues are due to a change in the folder browsing code
and are related to the ones originally described in this bug report,
but if you think otherwise I can report a new bug.

Thanks,

Berto

#838992#27
Date:
2017-02-14 14:54:44 UTC
From:
To:
Possibly related:

After upgrading to 1.7.2-1 from 1.5.something last weekend, I noticed
that hitting 'c' <tab> sometimes shows the contents of /var/mail instead
of the contents of ~/Mail as it used to.

I've since found out that if hitting 'c' and <tab> is the first thing
you do after starting mutt, the behaviour is like it used to be:
repeated tabs switch between showing the subscribed folders and the
total contents of ~/Mail.  However, if you hit 'c', <tab>, 'q', <enter>
(you didn't see any folders you wanted to change to) and then again
hit 'c' and <tab> now you see the contents of /var/mail instead?!

I.e. the behaviour changes if you abort the 'c' action, which is very
unexpected.


Paul

#838992#32
Date:
2017-07-02 20:07:12 UTC
From:
To:
Here's one other effect of the new folder navigation style that is
very annoying.

I have my e-mail locally in ~/mail, and let's say that I want to send
an new message with a few attachments.

When I'm in the Compose menu, I can press 'a' ('attach-file') to
select a file. Then I can navigate the filesystem (starting from
~/mail) to look for the file that I want to attach (let's say it's in
~/work/documents/reports/) and select it from there.

If I want to attach a new file, previous versions of Mutt would
start the navigation from the last directory, so I can attach 4 or
5 files very easily. The new versions forget the previous directory
and start again in ~/mail, forcing me to navigate every time to
~/work/documents/reports/. I can work around this by using tags and
the 'tag-prefix' command but the new behavior is quite annoying and
counter-intuitive.

Berto

#838992#37
Date:
2019-01-25 16:47:44 UTC
From:
To:
how are you
Can I ask you for a service?
please answer me it is very urgent

Gerard Rondel.

#838992#42
Date:
2019-03-15 10:59:49 UTC
From:
To:
How are you

Can I work with you for my project?
please answer me, it is very urgent.

Katelyn R.

#838992#47
Date:
2021-12-14 04:52:47 UTC
From:
To:

The emails in this ticket all actually show NeoMutt in the "package
specific info" section.

I can't reproduce the bug, so perhaps it was a temporary NeoMutt bug?

Would someone confirm they can produce this with the latest *Mutt*
release.  If not, perhaps we can close this ticket.

#838992#52
Date:
2022-05-06 20:42:56 UTC
From:
To:
This bug report was made when the NeoMutt patches were applied to Mutt.
Can't duplicate.  No response from original reporters.