Getting error "no entry" when using cd in some directories. #101

conradludgate · 2019-09-21T12:06:47Z

What did you expect to happen?
enhancd to let me traverse all local directories

What actually happened?
In only a certain subset of directories, I get either the "no entry" response when I give no arguments, or if I provide .., it won't actually change to the directory I selected.

Output

no entry

Additional context
This only seems to happen in a directory named c++ (~/Projects/c++). Maybe it doesn't work with non alphanumerics.

The text was updated successfully, but these errors were encountered:

conradludgate · 2019-09-21T12:08:05Z

I moved the directory to be cpp instead and it works fine now

babarot · 2019-09-24T08:10:14Z

Seems fixed. Please check it out with latest master.

conradludgate · 2019-09-24T08:15:18Z

Seems to be, can't reproduce the issue

babarot · 2019-09-24T08:19:27Z

Can I say done?

a5ob7r · 2019-09-25T11:45:43Z

Hello, @b4b4r07. I think this problem is rather happened by 0d39876. It is conflicting of grep matcher selection options(-E and -F).

https://github.com/b4b4r07/enhancd/blob/0d39876a09b210798c3bde2dd89271bf8dbde506/src/filter.sh#L98-L101

https://github.com/b4b4r07/enhancd/blob/100b809043a04010ae836f25e4bbab07089e41ab/src/command.sh#L1-L11

$ grep -E -F ~/.enhancd/enhancd.log
grep: conflicting matchers specified

juliogc · 2019-09-25T21:20:27Z

Same here to me! I'm using enhancd via zplug but I don't believe that's the problem.
The traditional navigation goes well. but every time I need the fuzzy search I get the no entry message.

Fuzzy search engine - fzy

➜ sudo apt list --installed | grep fzy   
fzy/disco,now 1.0-1 amd64 [installed]

➜ echo $ENHANCD_FILTER     
fzy:fzf-tmux:fzf:peco:percol:gof:pick:icepick:sentaku:selecta

Current enhancd version/revision

* 0d39876 - (HEAD -> master, origin/master, origin/HEAD) Take care about escape char (2 days ago) b4b4r07

Error sample
Try to navigate between root / to ~/Desktop via fuzzy search

18:20 in /
➜ cd Desktop
no entry

18:20 in /
➜ cd ~                             

18:20 in ~
➜ cd Desktop

18:20 in ~/Desktop
➜ echo $PWD           
/home/jcorradi/Desktop

As @a5ob7r mentioned, I already have noticed grep conflict matchers:

➜ grep -EF ~/.enhancd/enhancd.log
grep: conflicting matchers specified

I tried to remove ~/.enhancd/enhancd.log and even uninstall/reinstall it again, but still having this problem.

LanikSJ · 2019-09-25T22:34:36Z

I can confirm when I go back to 2ccdaca which doesn't have the above fix the issue @a5ob7r and @juliogc are seeing is no longer there. I imagine if I backed out the above commit only in my fork same would be true.

juliogc · 2019-09-25T22:34:59Z

More infos:

I returned the repository revision to 2ccdaca and the things worked again.

* 2ccdaca - Do not use ternary operator (8 weeks ago) b4b4r07

juliogc · 2019-09-25T22:38:10Z

I can confirm when I go back to 2ccdaca which doesn't have the above fix the issue @a5ob7r and @juliogc are seeing is no longer there. I imagine if I backed out the above commit only in my fork same would be true.

Wow! Same idea on same time! lol

I'll try others revisions to understand when the things goes wrong.

juliogc · 2019-09-25T22:46:32Z

It seens to be the latest 0d39876 commit that adds -F on __enhancd::filter::exclude(). Every thing before this works fine.

* 0d39876 - (HEAD -> master, origin/master, origin/HEAD) Take care about escape char (2 days ago) b4b4r07

babarot · 2019-09-27T08:42:03Z

Oh, nice report. Thank you all. I couldn't get this behavior with my grep so couldn't find this problem.

Anyway I'll work on this problem.

enhancd introduces an issue with rev 0d39876 that prevents it from working properly on some situations. See babarot/enhancd#101 for details.

babarot · 2019-10-02T07:12:56Z

Hi, all.

Sorry for inconvenience 😞 I managed to fix this reported behavior. All seemed to get back before. Please check it out. Thank you!

Issue was fixed in babarot/enhancd#101

juliogc · 2019-10-02T15:01:52Z

Hey, @b4b4r07
I saw your work but I'm sad to say that the problem persists in my environment 😢
I really can not understand why the the grep flags are causing this issue 😕 I'm trying to better understand the root cause to collaborate with some code.

Here the steps I take to update:

Clean the old log

11:39 in ~/.enhancd
➜ mv ~/.enhancd/enhancd.log ~/.enhancd/enhancd.log.old

11:39 in ~/.enhancd
➜ touch ~/.enhancd/enhancd.log

Back to latest revision in zplug, shell reload and zplug update
Try some fzy cd

11:43 in ~/.enhancd
➜ cd Desktop 
__enhancd::cd::builtin:cd:5: no such file or directory: Desktop

11:43 in ~/.enhancd
➜ cd Desktop
no entry

Check log file

11:43 in ~/.enhancd
➜ grep -EF ~/.enhancd/enhancd.log
grep: conflicting matchers specified

PS: Even with the old enhancd.log I get a no entry in my face 😂

kampka · 2019-10-02T15:41:36Z

Just FYI this is fixed for me as of the latest master.
@juliogc I had a quick look at your dotfiles and it seems like you are using a Mac. My guess is that MacOS ships a different grep than most linux do (GNU grep), likely some BSD version with different bugs as GNUs

juliogc · 2019-10-02T16:08:47Z

Just FYI this is fixed for me as of the latest master.
@juliogc I had a quick look at your dotfiles and it seems like you are using a Mac. My guess is that MacOS ships a different grep than most linux do (GNU grep), likely some BSD version with different bugs as GNUs

Thanks for your advice, @kampka, but you possible dived into old MacOS setup files that I keep in the repo for historical purposes, but I'm in Ubuntu 19.04 and the grep I use is the distro built in that I believe it's the GNU release.

➜ uname -a
Linux (hidden user/host names) 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

a5ob7r · 2019-10-03T06:35:34Z

Hello, @juliogc. When it occured "no entry" using enhancd in your environment, does it have a destination directory path in your enhancd.log file?

# when
$ cd Desktop

no entry

# the entry in enhancd.log
$ grep Desktop ~/.enhancd/enhancd.log

/home/user/Desktop

juliogc · 2019-10-03T17:48:06Z

Hello, @juliogc. When it occured "no entry" using enhancd in your environment, does it have a destination directory path in your enhancd.log file?
# when
$ cd Desktop

no entry

# the entry in enhancd.log
$ grep Desktop ~/.enhancd/enhancd.log

/home/user/Desktop

Hi, @a5ob7r ! I checked out the log file with tail -f and it seems to do nothing when no entry appears. 😞

a5ob7r · 2019-10-04T07:29:48Z

Hi, @juliogc. Thank you for your replay appnding gif! 👍

Did you use an AUTO_CD option of zsh to change directory? Maybe, implicit cd of AUTO_CD and explicit cd of enhancd (= __enhancd::cd) are not same. You need use explicit cd of enhancd to write a directory entory to enhancd.log. Please try using explicit cd of enhancd once.

Implicit cd

$ grep Desktop ~/.enhancd/enhancd.log

# None

# in zsh with AUTO_CD
$ ~/Desktop

$ grep Desktop ~/.enhancd/enhancd.log

# None

Explicit cd

$ grep Desktop ~/.enhancd/enhancd.log

# None

$ cd ~/Desktop

$ grep Desktop ~/.enhancd/enhancd.log

/home/user/Desktop

juliogc · 2019-10-04T20:02:01Z

@a5ob7r Usually I use to navigate via implicit cd, but I really doesn't know that it was a feature from zsh 😂 I thought it was related to enhancd.

Btw, here are another sample using explicit cd.

a5ob7r · 2019-10-04T23:24:49Z

@juliogc I also had a similar experience, too. 😆

Did you solve your problem?

juliogc · 2019-10-07T16:25:45Z

@a5ob7r this weekend I spent more time making some tests but I don't found any final solution 😢 But there are two workarounds that you could try:

If you made a backup from your ~/.enhancd/enhancd.log, you can make it active again and go to the latest revision 122a13b that it will back to work again.
If you don't made any backup, just lock the plugin in the 718bd31 revision and it it will work fine too.
zplug "b4b4r07/enhancd", from:github, at:718bd31, use:init.sh

The most worrying thing that I found in the whole process is that I tried to start a clean terminal setup with a fresh install from zsh, zplug and enhancd (without any ~/.enhancd/enhancd.log) and the plugin refuses to work with the same no entry error.

babarot · 2019-10-08T04:11:37Z

Hey all, sorry for late response...!

Hmm, it's strange.. It didn't happen in my environment. Because I removed conflicting flags from grep command. Could you @juliogc tell me your grep command version? I wanna investigate why this happen in your env.

juliogc · 2019-10-08T22:04:54Z

Don't worry, @b4b4r07 !

Here some useful outputs:

➜ grep --version 
grep (GNU grep) 3.3
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others; see
<https://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS>.

➜ zsh --version
zsh 5.5.1 (x86_64-ubuntu-linux-gnu)

➜ zplug --version 
2.4.2

stale · 2019-10-22T22:15:51Z

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

juliogc · 2019-10-23T00:38:53Z

Hello, guys, just a simple update: I'm using now the 9ac6887 revision and it backed to work properly.
My apologies to not inspect the full code to understand the reason, but my life backs to normal since that update.

Thank you everyone!!

stale · 2019-11-06T00:47:53Z

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

stale · 2019-11-27T05:30:31Z

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Paiusco · 2020-07-24T20:38:48Z

I think the issue I'm having here is the same.

fish, version 3.1.2
---
grep (GNU grep) 2.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
----
fzf --version
0.21.1 (334a4fa)

Consider the tree:

├── Backup-Trabalho
├── Desktop
├── Documents
├── Downloads
├── test-folder
        └── foo-bar
                └── foo-bar-example
└── WorkRelated

~
$ cd WorkRelated/

~/WorkRelated
$ cd download

~/Downloads
$ cd workrelated

~/WorkRelated
$ cd backup
no entry

~
$ 

--------

~
$ cd example (doesn't get me any way close to /test-folder/foo-bar/foo-bar-example/)
-------

~
$ cd bar
no entry

~
$

Also, anytime the no entry happens whenever dir I'm in, I'll be sent out back to ~/ for some reason. Should it be strictly necessary to write the complete full name [capital letters included] to expect it to work? (I'm just starting with the feature :) )

It looks like I'm having most of the problems with - on the dir names and capital letters too.

babarot · 2023-03-31T08:25:59Z

It's maybe fixed now on latest master. Because I did some big changes. Close once but feel free to let me know if you have still some problems

babarot closed this as completed in 0d39876 Sep 24, 2019

kampka added a commit to kampka/dotfiles that referenced this issue Sep 28, 2019

[zsh] Pin enhancd version

fdf28eb

enhancd introduces an issue with rev 0d39876 that prevents it from working properly on some situations. See babarot/enhancd#101 for details.

babarot reopened this Oct 2, 2019

babarot closed this as completed in ff6040a Oct 2, 2019

babarot added the kind/bug A bug; unintended behavior label Oct 2, 2019

kampka added a commit to kampka/dotfiles that referenced this issue Oct 2, 2019

[zsh] Unpin enhancd

5bd09c7

Issue was fixed in babarot/enhancd#101

babarot reopened this Oct 2, 2019

stale bot added the stale label Oct 22, 2019

stale bot removed the stale label Oct 23, 2019

stale bot added the stale label Nov 6, 2019

stale bot removed the stale label Nov 13, 2019

stale bot added the stale label Nov 27, 2019

babarot removed the lifesycle/stale label Mar 25, 2023

babarot closed this as completed Mar 31, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Getting error "no entry" when using cd in some directories. #101

Getting error "no entry" when using cd in some directories. #101

conradludgate commented Sep 21, 2019 •

edited

Loading

conradludgate commented Sep 21, 2019

babarot commented Sep 24, 2019

conradludgate commented Sep 24, 2019

babarot commented Sep 24, 2019

a5ob7r commented Sep 25, 2019

juliogc commented Sep 25, 2019 •

edited

Loading

LanikSJ commented Sep 25, 2019

juliogc commented Sep 25, 2019

juliogc commented Sep 25, 2019

juliogc commented Sep 25, 2019

babarot commented Sep 27, 2019

babarot commented Oct 2, 2019

juliogc commented Oct 2, 2019

kampka commented Oct 2, 2019 •

edited

Loading

juliogc commented Oct 2, 2019

a5ob7r commented Oct 3, 2019

juliogc commented Oct 3, 2019

a5ob7r commented Oct 4, 2019

juliogc commented Oct 4, 2019

a5ob7r commented Oct 4, 2019

juliogc commented Oct 7, 2019

babarot commented Oct 8, 2019

juliogc commented Oct 8, 2019

stale bot commented Oct 22, 2019

juliogc commented Oct 23, 2019

stale bot commented Nov 6, 2019

stale bot commented Nov 27, 2019

Paiusco commented Jul 24, 2020 •

edited

Loading

babarot commented Mar 31, 2023

Getting error "no entry" when using cd in some directories. #101

Getting error "no entry" when using cd in some directories. #101

Comments

conradludgate commented Sep 21, 2019 • edited Loading

conradludgate commented Sep 21, 2019

babarot commented Sep 24, 2019

conradludgate commented Sep 24, 2019

babarot commented Sep 24, 2019

a5ob7r commented Sep 25, 2019

juliogc commented Sep 25, 2019 • edited Loading

LanikSJ commented Sep 25, 2019

juliogc commented Sep 25, 2019

juliogc commented Sep 25, 2019

juliogc commented Sep 25, 2019

babarot commented Sep 27, 2019

babarot commented Oct 2, 2019

juliogc commented Oct 2, 2019

kampka commented Oct 2, 2019 • edited Loading

juliogc commented Oct 2, 2019

a5ob7r commented Oct 3, 2019

juliogc commented Oct 3, 2019

a5ob7r commented Oct 4, 2019

juliogc commented Oct 4, 2019

a5ob7r commented Oct 4, 2019

juliogc commented Oct 7, 2019

babarot commented Oct 8, 2019

juliogc commented Oct 8, 2019

stale bot commented Oct 22, 2019

juliogc commented Oct 23, 2019

stale bot commented Nov 6, 2019

stale bot commented Nov 27, 2019

Paiusco commented Jul 24, 2020 • edited Loading

babarot commented Mar 31, 2023

conradludgate commented Sep 21, 2019 •

edited

Loading

juliogc commented Sep 25, 2019 •

edited

Loading

kampka commented Oct 2, 2019 •

edited

Loading

Paiusco commented Jul 24, 2020 •

edited

Loading