-
Notifications
You must be signed in to change notification settings - Fork 8
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
ee-rg get: cat: /tmp/ee-rg.tmp: No such file or directory #19
Comments
Could you enable |
ee-yazi opening: cat: /tmp/ee-yazi.tmp: No such file or directory |
what's your |
/Users/username/.emacs.d/elpaca/builds/eee/eee.elc |
What's the value of `(ee-script-path "eee-rg.sh")`?
…On Fri, Oct 18, 2024 at 8:13 AM yibie ***@***.***> wrote:
/Users/username/.emacs.d/elpaca/builds/eee/eee.elc
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALCAINRDIYZPV2575DGCVBTZ4BHBPAVCNFSM6AAAAABPVWD54KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRQHEYDCNBXGM>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
/Users/username/.emacs.d/elpaca/builds/eee/eee-rg.sh |
can you execute |
also, please update |
I can execute the |
I had updated
Looks like the command had been executed. But I check the |
Could you execute `cd /Users/username/ && /Users/username/.emacs.d/
elpaca/builds/eee/eee-rg.sh` in your terminal, what't the output?
…On Fri, Oct 18, 2024 at 11:59 AM yibie ***@***.***> wrote:
I had updated eee.el, now execute ee-rg, shows log:
wezterm --config enable_wayland=false --config enable_tab_bar=false --config initial_cols=180 --config initial_rows=50 --config window_decorations=\"NONE\" -e bash -c 'cd /Users/username/ && /Users/username.emacs.d/elpaca/builds/eee/eee-yazi.sh > /tmp/ee-stdout-ee-yazi.tmp'
ee-rg: cd /Users/username/ && /Users/username/.emacs.d/elpaca/builds/eee/eee-rg.sh > /tmp/ee-stdout-ee-rg.tmp
Looks like the command had been executed. But I check the /tmp/ dir, no
ee-* files in there still.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALCAINRGORAXVKPJKT5YDBDZ4CBQVAVCNFSM6AAAAABPVWD54KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRRGI4DINJUGM>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
why you don't have eee-rg.sh file? it's not expected.
…On 10/18/24 3:12 PM, yibie ***@***.***> wrote:
|zsh: permission denied: /Users/chenyibin/.emacs.d/ zsh: no such file or
directory: elpaca/builds/eee/eee-rg.sh |
—
Reply to this email directly, view it on GitHub <https://github.com/
eval-exec/eee.el#19#issuecomment-2421613407>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
ALCAINWYUM657PENASTX3WDZ4CYF7AVCNFSM6AAAAABPVWD54KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRRGYYTGNBQG4>.
You are receiving this because you were assigned.Message ID: <eval-exec/
***@***.***>
|
why you can't `cd /Users/chenyibin/.emacs.d/`?
…On 10/18/24 3:35 PM, ***@***.*** wrote:
why you don't have eee-rg.sh file? it's not expected.
On 10/18/24 3:12 PM, yibie ***@***.***> wrote:
> |zsh: permission denied: /Users/chenyibin/.emacs.d/ zsh: no such file
> or directory: elpaca/builds/eee/eee-rg.sh |
>
> —
> Reply to this email directly, view it on GitHub <https://github.com/
> eval-exec/eee.el#19#issuecomment-2421613407>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/
> ALCAINWYUM657PENASTX3WDZ4CYF7AVCNFSM6AAAAABPVWD54KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRRGYYTGNBQG4>.
> You are receiving this because you were assigned.Message ID: <eval-
> exec/ ***@***.***>
>
>
|
I just forgot to change the path to my actual path, so I encountered an error. After changing it, rg was able to start normally in terminal. |
Then ee-rg works? |
No, just show the message like before. WezTerm didn't start. |
what's `getenv PATH` in your emacs? Does wezterm in the PATH?
…On 10/19/24 11:39 AM, yibie ***@***.***> wrote:
No, just show the message like before <https://github.com/eval-exec/
eee.el/issues/19#issuecomment-2421284543>. WezTerm didn't start.
—
Reply to this email directly, view it on GitHub <https://github.com/
eval-exec/eee.el#19#issuecomment-2423548353>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
ALCAINWDP62ZHTXK77TJ6QTZ4HH5NAVCNFSM6AAAAABPVWD54KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTGU2DQMZVGM>.
You are receiving this because you were assigned.Message ID: <eval-exec/
***@***.***>
|
After reset the PATH of wezterm, execute The system windows doesn't focus on wezterm. |
I guess it's related to your window manager's "Focus stealing prevention" related settings.
…On 10/20/24 5:38 PM, yibie ***@***.***> wrote:
After reset the PATH of wezterm, execute |ee-rg|, then wezterm start,
and works normally, but there is another problem:
The system windows doesn't focus on wezterm.
—
Reply to this email directly, view it on GitHub <https://github.com/
eval-exec/eee.el#19#issuecomment-2424781983>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
ALCAINQLVLPG4C7SWZ6G2HLZ4N22FAVCNFSM6AAAAABPVWD54KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUG44DCOJYGM>.
You are receiving this because you were assigned.Message ID: <eval-exec/
***@***.***>
|
Thank you, I'm using macOS, the problem isn't relate to you, it's all macOS fault. Let me figure it out. |
My current workaround is using Hammerspoon to watch the WezTerm. When WezTerm launches, it automatically focuses the WezTerm. hs.application.watcher.new(function(appName, eventType)
if eventType == hs.application.watcher.launched and appName == "wezterm-gui" then
local app = hs.application.get(appName)
if app then app:activate() end
end
end):start() |
Every command with "ee-...", error message shows up like this:
My env:
MacBook Pro M1 Pro, macOS 15, emacs 30.0.91.
The text was updated successfully, but these errors were encountered: