I don't see how that stack overflow answer is related to your case where you have source blocks of different languages, alternating, tangling to the same HTML file.
But I can kind of see why you are seeing the output this way. I have probably designed my Org tangling project in #Nim to do the same way.
> people don't have time and need someone responsible to to fix it right now this second. That's just how it is.
Yeah, that's sad. Free and open source software like #Emacs has spoiled me.
If something is broken, I try to fix it.
If I cannot, I ask for help, and then I can fix it.
If the fix would be nice for the whole community, I can send a patch and have it fixed for everyone.
I cannot do that for the closed source commercial products out there.
> I wouldn't go so far as to say @jrss was incorrect.
The help you get there is definitely faster than the help I get for commercial products. An example: I created a support ticket for #perforce. I get an email that they received the ticket. Then on the next day, I receive an "update" that the ticket has been forwarded to the tech team. Then in third email after a day or two, they say that they have created an enhancement request. End result: My problem is not yet solved.
> it doesn't have a hot-line for support
You are spreading incorrect info!
Simply email your query, anything about Emacs to
That's the best Emacs "hot-line". You typically get responses within 12 hours over there.
Example: Here's a recent question I asked there and someone replied with the exact info I needed: https://lists.gnu.org/r/help-gnu-emacs/2019-01/msg00044.html
I do agree that the user needs to commit some time to learn this awesome editor; after all it's not some Windows Notepad :P
This might be an ignorant question, but how is it true that #nim is *both* compiled to C *and* garbage collected? I would have thought that anything that's compiled to C would need to run without GC…unless nim compiles its runtime into C as well? But if it does that, how does it manage to have such small binary sizes?
> What about you consider, using raw html ditching org/hugo?
- I am not an HTML expert, and also I like my content source portable.
- I like that the same #orgMode source can be exported to HTML or PDF or Markdown, anything I like.
- I like to separate content from structure.
- The "signal to noise" ratio in HTML is too low, and it's too tedious to add that needed "noise", which I leave to static site generators (#Hugo).
So I don't see myself using raw HTML.
> well, the point is to chat with you the person, have fun.
Honestly, I don't video chat much. I more prefer text chats and emails.
> practically, i have 0 chance using hugo.
It's understood that you have no problems with your current flow, there's no reason to switch.
The Org syntax draft AFAIK hasn't been updated in a while, and I'd assume that Nicolas would have been the original author of that; may be he wrote that before implementing org-element.el.
If you have questions about that draft or need clarification, please send an email to the Org mode mailing list.
There are many other awesome frequent contributors and I apologise for not being able to list them all here.
Summary: Nicolas is the most active Org mode contributor for quite some time, and he's a great code reviewer and mentor too - 2/3
That's correct. Nicolas is not the official"maintainer", but for the past few years following and contributing to #orgMode, he's the active lead guy. He knows most of the Org mode code in and out and is the primary contributor for all the big Org mode features at least Org 9.0 onwards (and Org 9.0 development began, I think, 5-6 years back).
Bastien is the official maintainer, and takes care of cutting the Org mode releases - 1/3
- Build a simple web app
- It's done! Oh, wait, I should add a README
- Ok, released!
- Build a simple CLI
- It's done! Oh, wait, I should add a README
- Oh, wait, I should have built-in `--help` info
- Oh, I guess I should really have a man(1) page
- Oh, and shell completions would be nice…
- Oh, and if I've got a man page and completion scripts, I guess I should have a makefile
- So I guess I should update the README with installation instructions…
- What was I doing, again?
@codesections You forgot the adding tests and creating a documentation webpage parts :)
There actually not much to the setup. I'll post a short gif screencast of my flow when I get a chance later today.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!