Fork me on GitHub

Anyone using emacs from docker?


I haven't given much thought, but I guess terminal emacs should be straightforward, gui emacs much harder


I haven't had the time to try it yet, but even in gui mode it seems straightforward to use


xhost +local:root # WARN: this comes with security issues
docker run -it --rm -e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix silex/emacs


Just tested it, I only played with it for 5 minutes but it seems to work flawlessly in GUI mode


this seems like a good place to ask: how can you do remote pair-programming with emacs? I went thru but nothing is very modern there... in the past i did quite a lot of pairing over the built-in VNC support of macOS, but that's often not feasible because of bandwidth constraints. (btw, i can highly recommend using to extremely easily put the pairing workstations on the same virtual subnet, so u can just connect to them with open when the Remote Management is turned on in System Preferences / Sharing and you set the Anyone may request permission to control screen option under the Computer Settings... dialog)


a colleague of mine mentioned that he heard in some podcast that TRAMP mode can help somehow with remote pairing too, but i suspect that's also some clunky, non-realtime solution... i made the lockstep module work once, btw. that was very promising, but then it stopped working... it's just too finicky


@onetom I keep meaning to try the floobits layer for Spacemacs for collaborative editing. The package itself is at and I would be interested to know the experiences of anyone who has tried this.


i tried floobits a few years back when it came out, but what was off-putting for me is that i had to upload my source code to their servers to be able to collaborate on it


on top of that it meant i had no latest version available locally, which i could run. now this all might have changed since, but i doubt, since that would require to change the fundamentals of their idea


ah, i remember now, what was my biggest grief. even though we could collaborate on editing the source code files, floobits doesn't help with sharing the experience of running it and interacting with the program.


as i see now, they have some supporting software to ease these pain-points: •


@U05254DQM you have great content, btw! i've just discovered it recently. i think it will help tremendously to get my colleagues into clojure easier and quicker.


Thanks for the feedback, very helpful. It would be great to have a simple to use, editor to editor(s) collaboration tool that you can use with any editor. I tried the Atom Teletype (from Atom to Atom) and that worked okay, so long as you didnt switch files... so not great for a project.


Oh, thanks for the comment about my content. There is so much more to do, so thanks for keeping me motivated 🙂


we just dialled down our expectations and currently trying to use the terminal version of emacs within tmux (but via for easy configuration, but of course it also has some issues under macOS). nothing is as well-polished as jetbrains ides 😞


i tried tmate before. not too bad indeed. i will keep it in mind, thanks!


im not sure how to google for this: i would like the point to move from the beginning of a line to the end of the previous line, when i press the left arrow, or h in evil mode. how can i configure spacemacs to behave like this?


why not just k and then $?


what is the current behavior? hitting left error does precisely that for me


@onetom have a look at customizing Evil Cross Lines and check out the docs for evil-backward-char

🙏 4
Eric Ihli21:01:52

Damn this has me confused and I can't find anything online to help. (some-fn some-args) prints out the expected string in the mini-buffer. (with-current-buffer (get-buffer-create "foo") (insert (some-fn some-args))) only inserts about half of the expected string. Anyone have any idea why? Do I need to flush something? Possible encoding issue?

Eric Ihli21:01:09

Ah. Hm. So. My function calls shell-command-to-string. I just saved the result off and ran the with-current-buffer again and it worked. So it must be something with stdout.