Fork me on GitHub

I posted this question on reddit but no luck


I've installed emacs on a fresh Ubuntu 17.10 with i3. What's this white/grey border around the window and, more importantly, how do I remove it?


could it be your i3's active window border? It’s color is configured using client.focused variable ( and presence using the default_border ( Or is this border only present for the Emacs?


This is GUI Emacs, not Terminal - and that's my preference. Only shows on Emacs so inclined to think it's not a WM thing.

Nikita A Dudnik08:04:33

Hello everyone 👋


@bozhidar @eggsyntax Honestly, “because lisp” is a pretty bad answer when someone asks why something works the way it does.


@munen I have the same setup on another PC and there's no borders 😕


I honestly have no clue where this border is coming from


Well, not to be tedious or something - but there's a good chance it's not exactly the same setup, right?(;


@cfleming Well, you can’t easily discourage historical conventions - different comment headings were meant to have different meanings and this still holds true for many people using Clojure. If you think about it many people in programming are “because X”. 🙂


@cfleming how would you feel about adding the option of using ;; for line comments? That would go a long way toward supporting mixed-IDE teams. (I filed an issue requesting that feature yesterday, BTW -- )


@eggsyntax Sure, I could do that, but Emacs could also equally add an option to not move single ; comments out to 60 chars or whatever, which if I understand correctly is the main problem. The only reason that I can tell for not doing that is historical.


@cfleming granted that Emacs could also change here. I think there's almost no chance that Emacs itself will make this change, since Clojurians are just a sliver of the Emacs community. And clearly @bozhidar dislikes the idea of changing it in CIDER. So I'm appealing to you 🙂 FWIW, if you were to take a poll of Clojurians, I think a large majority of them would either a) say that ;; for line comments is correct, or b) have no opinion either way. I've never heard anyone argue that ; is the more correct option (until now, maybe?). Historical tradition certainly isn't law, but in the absence of good arguments to the contrary, it seems like a reasonable way to go (or at least to have an option for). If there are arguments for ; (other than saving a keypress), I'd love to know about them. Anyhow, I certainly don't think you're under any obligation to change it -- it's just that it would be nice if there were some good way to avoid constant reindentation on mixed Cursive/Emacs teams. If I can squeeze out the time, I may try to at least come up with a workaround for Emacs (I use Cursive sometimes, but I don't know much about how to do Cursive customization of that sort).


@eggsyntax Sure, I’ll add the option in Cursive - I don’t have strong feelings either way, and I’ve added options for Emacs compatibility previously (like one space list indent). But I’ve literally never felt the need for more than ; in my comments - it seems to add no information at all.


But I accept that I’m doomed to emulate Emacs’ weird corners for mixed-editor teams 🙂


That's fantastic, @cfleming! Thank you so much for being willing to do that 🙇


FWIW - I’m not strongly opposed to making this configurable, I’m just juggling a million projects and a ton of work. Seems to me on the Emacs side my time can be better spent elsewhere.

👍 8

Btw, there’s one advantage of distinct comments - you can afterwards easily search forward for them. (e.g. I often look specially for ;;;).


I guess that becomes useful after it becomes a habit, though. 🙂