Timeline for How can I disable some code without commenting it out or removing it?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2023 at 15:51 | history | edited | Drew |
edited tags
|
|
| Mar 18, 2023 at 15:40 | answer | added | Drew | timeline score: 2 | |
| Mar 18, 2023 at 15:34 | history | edited | Drew | CC BY-SA 4.0 |
edited title
|
| Mar 18, 2023 at 14:21 | answer | added | John Kitchin | timeline score: 1 | |
| Mar 18, 2023 at 13:16 | comment | added | phils | @Shynur Emacs breaks the lines for you, if necessary, when you comment out a region, and there's a standard key binding for joining lines if uncommenting again. I can only speak for myself of course, but I don't personally find it annoying. | |
| Mar 18, 2023 at 11:36 | comment | added | Philippe-André Lorin |
@phils off conveys my intention to turn code off. Comments can be used for a lot of other purposes. Also, sometimes, albeit infrequently, I like disabled code to keep being editable without loosing indentation and highlighting. For instance, it’s harder to read commented-out, not highlighted, code.
|
|
| Mar 18, 2023 at 11:24 | comment | added | shynur |
@phils: The way Elisp handles ; is based on lines of text instead of S-structures. If we want to comment some code, we first need to make them separate from the code snippet. Sometimes it is annoying. It would be nice to use an S-expression-based approach to comment some code. I also asked a question which is related to this topic.
|
|
| Mar 18, 2023 at 9:42 | comment | added | phils |
What's the problem with commenting things out? Selecting the code and typing M-; is easy, no? Wrapping your off form around something still requires acting on the beginning and the end of the forms you're disabling, so I don't see an advantage of that over the commenting workflow which acts on those exact same positions.
|
|
| Mar 18, 2023 at 9:29 | history | asked | Philippe-André Lorin | CC BY-SA 4.0 |