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

wrong pass-view behaviour on dirname #36

Open
firmart opened this issue Jun 16, 2019 · 2 comments
Open

wrong pass-view behaviour on dirname #36

firmart opened this issue Jun 16, 2019 · 2 comments

Comments

@firmart
Copy link

firmart commented Jun 16, 2019

A minor issue.
If I press <RET> on the directory name www.linkedin.com in the below example,
it shows me the pass-view of the entry bitbucket.org. I think that the expected behaviour should show No entry at point just like it actually does on ├── symbol.

├── bitbucket.org
├── www.linkedin.com
    ├── account1
    ├── account2
    ├── account2
@ktetzlaff
Copy link

Furthermore, pass-mode doesn't handle the following situation:

├── bitbucket.org
├── www.linkedin.com.gpg
├── www.linkedin.com
    ├── account1
    ├── account2
    ├── account2

where there is a password entry (www.linkedin.com.gpg) and a directory name (www.linkedin.com) which share the same basename. The pass cli doesn't have a problem with this, but in pass-mode, www.linkedin.com.gpg is inaccessible.

@doolio
Copy link
Contributor

doolio commented Dec 5, 2023

@ktetzlaff can you confirm the www.linkedin.com.gpg is not named www.linkedin.com.gpg.gpg (typically the .gpg extension is omitted from the tree output)? If it is that could be the reason you observe this behaviour.

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

No branches or pull requests

3 participants