Live data from Hacker News

I wish Asciidoc was more popular

pdx.su

41–50 of 124 posts

Re: I wish Asciidoc was more popular

#41

"the ability to format and fit content in your editor, loosely independent of how it would be presented to the user" ?? Markdown is the opposite, no? Ability to format text in an editor that looks sufficiently like formatted final text so you don't need to render it all the time. That's what I like about markdown anyway.

I was more referring to the behavior some markdown parsers have, which is that they (deliberately) make line-breaks significant.

Try writing something in your text editor of choice, and hard wrapping it at 80 columns. You then paste it into a github issue, and you'll see that the line breaks are preserved. It gets pretty annoying, even if all you have to do is join all the lines in the paragraph/section.

I'm not advocating for a total decoupling of presentation from raw code, but I do think that significant newlines are a point of particular irritation.

Re: I wish Asciidoc was more popular

#43
Asciidoc is a no-brainer. The TOC macro alone is a game changer.

Just wish the documentation were so absolutely awful -- extremely bare and hard to find examples. Enumerated values poorly explained, if at all.

Re: I wish Asciidoc was more popular

#44
post #35

Earlier quoted context omitted.

A lot of dependecies are pulled from the (recommended) asciidoc-dblatex package, which depends, indirectly, on x11 packages. Don't install the recommended packages (whose concept is anyway in conflict with keeping a system lean) and see what happens.

How to not install recommended packages? (there wasn't a choice, and anyway not installing recommended packages often implies - rightly or wrongly - security risks).

The `apt` tool provides the option `--no-install-recommends`.

If you want to disable the recommended packages installation by default, you can:

  echo 'APT::Install-Recommends "0";' > /etc/apt/apt.conf.d/99disable-recommends.conf
You may also want to disable the suggested packages:

  echo 'APT::Install-Suggests "0";' >> /etc/apt/apt.conf.d/99disable-recommends.conf

Re: I wish Asciidoc was more popular

#45
I love AsciiDoc and want to use it more. The main problem is, as noted, that it's hard to get this ruby library into whatever platform you want to deploy to. Consequently it's hard to build tooling based on AsciiDoc.

I've had a brief play with trying to implement AsciiDoc in Rust (and others have too, see https://github.com/Veykril/pagliascii). I got bored of trying to figure out what the semantics should be by reading the implementation and decided to wait until the upcoming specification effort at https://asciidoc-wg.eclipse.org/ bears fruit, the Zulip seems a bit more active recently

Re: I wish Asciidoc was more popular

#46
> For example, Markdown has a syntax for inserting a break, inside a paragraph. You put two space characters at the end of a line, and the parser will inject a line break.

Don't most Markdown implementations allow you to use an empty line as a paragraph separator as well?

Re: I wish Asciidoc was more popular

#47

> For example, Markdown has a syntax for inserting a break, inside a paragraph. You put two space characters at the end of a line, and the parser will inject a line break. Don't most Markdown implementations allow you to use an empty line as a paragraph separator as well?

Yes, and that differs from a line break inside a paragraph, which is what the author is discussing.

Re: I wish Asciidoc was more popular

#48

> For example, Markdown has a syntax for inserting a break, inside a paragraph. You put two space characters at the end of a line, and the parser will inject a line break. Don't most Markdown implementations allow you to use an empty line as a paragraph separator as well?

Yes, and that differs from a line break inside a paragraph, which is what the author is discussing.

Oh I never realized that was the difference, thank you.

Re: I wish Asciidoc was more popular

#49
post #26
post #17

Main killer for me - admittedly because I like sharp tools, and it used to claim to be 'lightweight': 'apt install asciidoc' (and I had to delete most of it, because - for the first time ever - I got an HN message about "comment too long"):- Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: asciidoc-base asciidoc-common asciidoc-dbla…

Probably because asciidoc recommends asciidoc-dblatex (used for producing LaTeX via docbook). Try 'apt install asciidoc asciidoc-dblatex-' to install just asciidoc without pulling in the other package.

How does that command work?

Re: I wish Asciidoc was more popular

#50

Earlier quoted context omitted.

Org is also just a file format with extensions available in VS Code, vim, sublime, and Atom. I've personally used the VS Code extension, I think it works just as well as the Markdown extension. [1]. https://orgmode.org/install.html

It's not just a doc format though, it's also a task manager format, a literate programming format, an everything format with no clear separation. I can't help but feel like it would be a lot more widely accepted if they divided it in multiple projects each with their own goals and requirements.

That is a much more challenging task - even if they had planned it from the get go. One of the reasons people gravitate to Emacs is that it is much easier to build integrated systems like Org mode.

The other barrier, of course, is that it doesn't really benefit existing Org mode users/developers.

Post reply on HN