Skip to content
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

change comment character to - #57

Open
holtzermann17 opened this issue Jan 23, 2019 · 2 comments
Open

change comment character to - #57

holtzermann17 opened this issue Jan 23, 2019 · 2 comments

Comments

@holtzermann17
Copy link

#7 asks the same basic question, but for Literate Haskell. I'm interested in making changes for compatibility with Lean, where comments are:

-- like this
--- or even like this :-)

What's the best way to make --- the first header level and ---- etc. the next levels after that?

@alphapapa
Copy link
Owner

alphapapa commented Jan 29, 2019

Hi,

I don't know. The emacs-lisp-mode code handles headings using strings of semicolons 3-or-more characters long, so you could probably study its code to find out how it works. AFAIK Outshine isn't designed to work that way, as it imitates Org. I doubt it would be simple to make a change like this to Outshine, as its code isn't designed to be flexible in that way. It might be better to try to implement something using outline-minor-mode, hideshow, origami, etc.

Long-term, this might be relevant to #53.

@tj64
Copy link

tj64 commented Jan 29, 2019

Hi,
as alphapapa says, outshine imitates org (outshine header = outcommented org header, e.g. ## * 1st level), with elisp as one exception since I had to adapt to the coding rules for emacs lisp libraries, no way around that (so outshine.el itself has ;;; 1st level header, otherwise melpa would not have excepted it.

A special case like this is always painful and should rather be avoided for peace of mind.
But I think the asteriks "*" is customizable in outshine (not in org), so you could try to customize it to "-".

But I have my doubt if it works ...

If you use outorg to, there would be a problem. Outorg then should read that outshine custom instead of simply assuming "*" for header levels, coding change needed.

Cheers
Thorsten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants