phil-s

You could also consider adding a *new* option to lando 3's ssh command which is like `-c` but works the way that lando 4 will work. E.g. `lando ssh -C...

Hopefully a standard solution will be added but, for the benefit of anyone else who needs this, here's what I've hacked together for local use in the interim... The first...

I've just updated to lando v3.20.8 and discovered that I needed to track down a new location for the `docker-compose` executable, which turned out to be this: ~/.lando/bin/docker-compose-v2.21.0 So adjust...

https://github.com/alphapapa/ement.el/issues/140 is related; you may find the code there useful.

#140 turned into #236 which has now been merged. I encourage any readers looking here because they'd like an IRC-style prompt to try out the options implemented in that PR...

> it's not "posframe" that's the issue, the issue is that a variable with a # value is saved. When burly tries to restore values, it needs to read values...

That seems to work, except... I managed to crash Emacs while I was testing, by running `bookmark-jump` for the bookmark in question a second time after having successfully visited it...

Ah, my apologies, this fell completely off my radar. I stopped using burly once I realised that Ement.el's Notifications buffer enabled me to eliminate the use-case I'd had for wanting...

FWIW the sh hack is a matter of script portability, and not really Emacs' fault. See http://stackoverflow.com/a/6259330 for details.

Ah, I see. Another option would be an alternate executable name (say, `elisp`). That would make `#!/usr/bin/env elisp` possible on any system, as `#!/usr/bin/env emacs --SCRIPT` still requires > 1...