I keep putting off making that change - the change itself is not hard, but since I don’t want to break existing working code, I want to provide an auto-migration tool for it, which is much more work
2 replies
maybe a feature flag to turn it on? so that the code written now can be validated?
Agree, that would be quite a lot of manual work, particularly since it would not be trivial to do it correctly by textual search/replace, so working from Elvish's internal representation would be the way to go I guess.
Exactly - deciding whether “foo = bar” should be converted to “var foo = bar” or “set foo = bar” requires knowledge of the scope, which can’t be done just by text processing, but it is some information that the Elvish compiler knows
I am using github.com/zzamboni/elvish-modules/terminal-title but it seems not working. My tmux pane name is stuck to be elvish. Will really appreciate if anyone could give me a pointer of how to troubleshoot :-) Thanks
it works for Terminal.app but not for tmux. I guess it's the control chars?
:point_up: Edit: I am using github.com/zzamboni/elvish-modules/terminal-title but it seems not working. My tmux window name is stuck to be elvish. Will really appreciate if anyone could give me a pointer of how to troubleshoot :-) Thanks
nvm i am working around using tmux rename-pane
I think tmux uses a different escape sequence: https://stackoverflow.com/questions/9747952/pane-title-in-tmux
i guess that is because it sets the pane name
and what i want to do is to set the window name
allow-rename [on | off]
Allow programs in the pane to change the window name using
a terminal escape sequence (\ek...\e\).
Allow programs in the pane to change the window name using
a terminal escape sequence (\ek...\e\).
You need to do a "set -g allow-rename on", and use that escape sequence
let me try another escape sequence
But the problem is that the name will stick even if you switch to another pane
that's fine for most cases though...
I remember I tried getting tmux's window title to work a long time ago and eventually gave up :)
the thing is automatic-rename does not work as in other shells... i have no idea why
haha maybe i would just use tmux rename-window for now
i tried other sequences but still not working
What makes Elvish special is that it doesn't have job control - so it always runs in the foreground, and this breaks tmux's automatic detection of which program you're running
btw is there a way to support Ctrl-Z?
i guess no because there is no job control?
that is a little bit inconvenient 🙈
I’m open to adding job control, but it’s quite low-priority for me since I personally never use it
Since you already use tmux, is there a particular workflow that you can’t do by opening another pane in tmux?
no really. it is just a habit bc sometime i do not have tmux running
like a muscle memory and sometimes just would not think if i have tmux now
I see. You'll have to manage without job control, unfortunately. Contribution is welcome too. :)
Hi all. I've got an experimental fork of elvish with
use supporting go plugins. I'd like people to look at it before a PR since it might be a breaking change. Check it out at https://github.com/kolbycrouch/elvish-plugins
I should elaborate. That repo has a script and some plugins I had messed around with for the last year or so. The actual elvish fork is a submodule in that repo. It changes the
use keyword to check the extension of the module argument, if it's ".so" it loads the plugin and returns the Ns symbol from it.
Neat. AFAICT the change is pretty small, so feel free to open a PR directly
One thing I realized is that plugins require cgo, which breaks reproducible build and cross-compilation, and introduces a dependency on libc (which is primarily a problem on Linux)
it's common to fork a process and do IPC with it for plugins on go to bypass the limitations of the native plugin system
So I won’t provide prebuilt binaries that have plugin support, and interested users will have to build Elvish from source. This is still better than you having to maintain a fork though
@pontaoski I’m aware of that approach, but it’s both more complicated and has limitations like you can’t introduce new data types
It also requires copying the data back and forth, which is probably not going to be a serious constraint for anything people do with Elvish though
Anyone has some code for integration of conda with Elvish?