I really haven't been able to find good editor tooling for asciidoc

markdown is everywhere and well supported

probably depends on what I was doing with it, honestly

It's for my blog. Hum, that's a good cons for asciidoc. I'm currently using Pandoc markdown, it's okay, but I find having to manage some of the extensions and filter a bit annoying. AsciiDoc looked interesting, especially its diagram support.

asciidoc looks amazing to me and maybe I was just bad about finding good editor support

the emacs stuff is sort of unmaintained best I could tell

oh wow the vscode one looks pretty decent

asciidooc is markup, just use any text editor

I find editor integration to be important

and so do a lot of people

asciidoc has a conception of document sets that are published together, and the ability to specify intradoc links. for me, that alone made it vastly superior to markdown for any scenario bigger than a single file

@U02N27RK69K if you are thinking of integrated preview support, VSCode is pretty good for AsciiDoc.

@U0K064KQV I prefer AsciiDoc over Markdown. I find it easier to express myself in adoc. It has a richer set of features.

> Any thoughts on asciidoc vs org-mode vs restructredText vs markdown? Yes. Lots of thoughts 😀 https://www.evalapply.org/posts/why-and-how-i-use-org-mode/ (see the section on "A pretty good example of my usage" as well as "But seriously, Emacs winkwink, amirite?" if you don't already use Emacs).

> It's for my blog. Aside: I'm also working on https://github.com/adityaathalye/shite, my dead-simple site/blog maker for myself, such that it is trivial to plug in any source text format for content (org, md, asciidoc etc.), along with any source -> HTML compiler (pandoc or whatever). Like so:

find content/ -type f -name *.org |
    shite_build_public_html \
        shite_proc_orgmode_content \
        shite_tidy_html > /dev/null

@U0K064KQV we are using asciidoc to document all kind of documents for our software: schemes, tables, diagrams. We use IntelliJ IDEA to edit asciidoc documents. It has integrated preview mode, grammar check etc. I found IDEA is most useful editor to work with this format. asciidoc allows us to publish our docs to various places: Confluence, Github, pdf, epub etc. Also asciidoc has great opensource editors like https://asciidocfx.com

asciidoc is super amazing. the ability to do admonitions alone is so so handy! it's my go to. For editing, I normally just edit in vim and have the page open in firefox with the Asciidoctor.js preview plugin enabled. As soon as I save the file in vim, the page in firefox reloads and I can see the changes instantenously.

I find Markdown together with MkDocs Materials to be the sweet spot for me. It is pretty feature rich and things look great out-of-the-box so I don't need to waste time using my non-existing design skills. It's what's used for http://calva.io. Key features for me are the info-boxes that I can easily choose if they start collapsed or expanded and wether they are communicate information, warnings, or errors. Also very nice search function.

I really like org-mode. It's got a lot of intelligence baked in there, plus tools like org-roam which can auto track backlinks. Wouldn't rule it out unless you don't want to be tied to emacs

https://curiousprogrammer.net/posts/2022-01-12-moving-to-cryogen#_asciidoc

I love Emacs org-mode, but I just can't get emacs to have usable performance in windows for whatever reason. I've tried org-mode plugin for VSCode but it's missing almost everything from org-mode and I now abandoned.

@U013YN3T4DA have you tried emacs running on linux under wsl using windows' new support for running x11 apps?

I was under impression that x11 support is only for wins 11.

ahhh so it is! my friend was telling me about it, I didn't realize he was on 11

I've used one of the third party x11 servers on windows 10 but can't remember how well emacs worked

windows 11 is out now, though. I should try it

i switched my personal blog to asciidoc and i like it, but i made what i think is a mistake to follow the asciidoc standard of 1 sentence per line. I find it really hard to read and write like that and wish I hadn't done it as it makes it hard to read the text version of old posts.

@UEENNMX0T I understand that everyone is different, but I personally like the https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line.

Yeah, that's the page that got me to try it out, but I found it doesn't work well for me. It's not how I think about source code either, lol.

I use Emacs on Windows with WSL2 and X410 as an x server. Works well

For those using org-mode, what's your setup to convert it to HTML? I think it be great for writing, as I use Emacs, but is there a command line to convert it that doesn't rely on Emacs? I think Pandoc technically has support for org, but not sure how good.

I've used ox-pandoc (via doom emacs) to export to html

I can't claim it's wonderful, I only used it a little, but it did work

Maybe one of the tools listed here will be useful enough? https://orgmode.org/tools.html Alternatively, maybe run emacs itself in batch mode? Some https://emacs.stackexchange.com/questions/14947/can-emacs-commands-be-called-from-a-shell-script.

Hum, thanks all. Seems nothing is perfect haha. Might stick with what I've got now 😛

tradeoffs, sigh :)

I’d like to voice my appreciation for restructured text; I’ve tried asciidoc and while it’s really good it didn’t really “gel” with me for some reason. RST was a bit intimidating at first but now I really like it for writing technical docs. Markdown is fine but I found it really limiting in its lack of e.g. admonitions, section references etc. Sure, you can use various extensions, but unless your language / blog engine of choice has good and complete support (as opposed to partial) for a specific superset of Markdown (e.g. Kramdown, GH Flavored Markdown) you’ll end up with your own weird dialect that may or may not be portable. RST and Asciidoc OTOH are quite established standards

Interesting, I'm using Pandoc Markdown, and my blog engine doesn't actually take markdown, but HTML directly, which Pandoc renders.

But its nice to see more native support of more powerful things from rst and asciidocs, that's actually what got me curious. I even wrote some of my own pandoc filters for extensions, but it gets tedious

(def orders {"b" 0 "a" 1 "d" 2 "c" 3})
(def to-sort (str/split "abcd" #""))
(sort-by #(get orders %) to-sort)

(sort-by orders to-sort)

Note that str/split returns a vector, which is indexable. Also, strings are indexable as well - no need to split them.

(def order [1 0 3 2])
(def to-sort "abcd")

(map #(nth to-sort %) order)

Wonderful. I was playing around in the REPL trying to golf it more and more. I do not think it can be done better.

How would you find the order indexes in the first place?

(def o (into {} (map (fn [[a b]] [b a]) (map-indexed vector "badc"))))
(sort-by o "acdbaac")
;; (\b \a \a \a \d \c \c)

Regarding your original question, would something like this be suitable?

(->> (map vector orders to-sort)
     (sort-by first)
     (map second))

Also a very nice solution!

Alternatively you could start with (zipmap orders to-sort)

(def s "badc")
;;=> #'user/s
(sort-by #(.indexOf s (int %)) "acdbaac")
;;=> (\b \a \a \a \d \c \c)

.indexOf is linear time though, but that is a good solution for small collections.

The answer is not whether you should but whether you want to. And if you write this message you probably do.

yeah that's the thing, it became unsustainable for me but I do like doing it

This is the newsletter right? Maybe make it monthly or bi-monthly? Any amount of morsels is a treat! 😆