epub-create VS enhanced-ruby-mode

It's in the repo i linked to upthread; in particular, please refer to this file at this commit, with the four instances of cat ${SPINE} | replaced with <${SPINE}[a].

In my own case, although i'm not active on any microblogging platform, i am a FOSS dev and, er, 'documenter', and i recently read up a bit on the EPUB standards to put together a guide and shell script for creating a minimal EPUB.

Last year i encountered a problem caused by LVM's build system relying on a bashism. And i recently release a simple shell script for creating EPUBs, which tries to avoid using non-POSIX functionality so that it's more likely to be usable on different systems/platforms.

i can reproduce this on my system, using my epub-create script i released just the other day. :-)

In the context of the Ruby snippet you shared, the indentation doesn't matter for what the code is doing, but in other contexts, the indentation *can( matter. For example, i recently wrote a shell script to create a minimal EPUB, which uses heredocs to create XML and XHTML files. If Emacs indented the 'headers' and 'footers' according to their position in the code structure, their indentation in the resulting files would be misleading (even though this wouldn't affect the validity of the markup).

All that said, a superficial search via package-list-packages with the MELPA repo enabled shows the existence of emh-ruby-mode, which might do what you require; but even if it doesn't, there's poly-ruby:

enh-ruby-mode for editing Ruby code