-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
insert blank lines when tangling #955
Comments
What do we think about expanding upon this idea and have closest heading in a comment as the delimiter where that makes sense? |
That requires knowing something about the syntax of the target language, since we need to know what its comments look like, which definitely isn't possible in general. It might make sense as a default-off option for supported filetypes. |
You are absolutely right. Limiting the support for this to supported languages makes sense, yes. I was thinking we on demand temporarily load tangle targets into buffer memory which triggers ftplugin and sets |
Ah, I see. Yeah, seems like it would be cool! |
I've pushed out an suggestion in #981 if you're interested. Continued thought in the same direction: |
I like the idea of adding information about a tangle job! @jonathf any extra behaviour with delimiters should definitely be put behind config flags where possible (most likely in the document metadata). The default behaviour should be as simple as can be :) |
Issues
Feature description
By default, when emacs tangles org-mode files, it inserts blank lines between code which originates in different blocks. This behavior makes for more readable output files---not the biggest deal with literate programming, but definitely useful. It's also probably good for the defaults to line up unless there's a reason for them not to.
Thanks for the great software--I'm currently trying to convert my ~2000 line config to norg so I'll probably have more issues to come. Happy to write a PR for this, doesn't seem too difficult.
Help
Yes
Implementation help
No response
The text was updated successfully, but these errors were encountered: