Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation and implementation of sidebar_short_path do not coincide #3614

Open
whitney-cumber opened this issue Jan 22, 2023 · 0 comments
Labels

Comments

@whitney-cumber
Copy link
Contributor

Expected Behaviour

The description of $sidebar_short_path and its actual effect should coincide.

Actual Behaviour

The description does not match its effect.

Steps to Reproduce

  1. Create mailboxes
$ mkdir /tmp/testmails
$ mkdir /tmp/testmails/foo/{cur,tmp,new}

$ mkdir /tmp/testmails/foo.bar.baz
$ mkdir /tmp/testmails/foo.bar.baz{cur,tmp,new}
  1. Create test neomuttrc
$ cat > /tmp/testneomuttrc
set folder=/tmp/testmails
mailboxes /tmp/testmails/foo
mailboxes /tmp/testmails/foo.bar.baz
set sidebar_visible
set sidebar_short_path
  1. Start Neomutt neomutt -F /tmp/testneomuttrc

  2. Observe that the mailboxes are listed as foo and baz

The documentation in neomuttrc states:

Setting sidebar_shortpath=yes will shorten the names relative to the previous name.

So I expect it to be foo and bar/baz as the previous mailbox name is foo and not foo/bar.

How often does this happen?

  • Always

When did it start to happen?

When I enabled $sidebar_short_path

NeoMutt Version

20220429

Extra Info

If it is concluded that the documentation needs to be adapted, I'm willing to provide an draft/PR.

Personally I find the documented behaviour to be the better one as it does not require to insert a dummy mailbox foo/bar when using indention in the sidebar.

Compare:

foo
  bar.baz

vs

foo
  bar
    baz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant