unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: lisa-asket@perso.be
To: "Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 49346@debbugs.gnu.org
Subject: bug#49346: headings when using sh-mode
Date: Sun,  4 Jul 2021 19:18:08 +0200 (CEST)	[thread overview]
Message-ID: <ea-mime-60e1ed50-6a61-1890c5ee@www-8.mailo.com> (raw)
In-Reply-To: <87bl7i421c.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]

I have been using 



# h1

# h2

# h3



This is similar to defining headers in html without ending up using long repeating symbols 

such as `#####` or `*******`.  The number at the end defines the headline level.



From: Lars Ingebrigtsen <larsi@gnus.org>
To: lisa-asket@perso.be
Subject: bug#49346: headings when using sh-mode
Date: 04/07/2021 15:54:55 Europe/Paris
Cc: 49346@debbugs.gnu.org

lisa-asket@perso.be writes:

> I enabled `outline-minor-mode` and found that by default `sh-script`
> uses `*`, `** `, `***` as headings. Because the headings are not part
> of comments, my bash script breaks if I use headings in this way.
> Headings normally start with the comment character.

`sh-mode' has no support for outlining, so `outline-minor-mode' just
uses the default values for `outline-regexp'. So I guess this is a
wishlist item for adding support for outlining in `sh-mode'?

Does anybody have a suggestion for what that should be in `sh-mode', or
whether this doesn't really make sense for `sh-mode'?

-- 
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no





[-- Attachment #2: Type: text/html, Size: 1550 bytes --]

  reply	other threads:[~2021-07-04 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  0:19 bug#49346: headings when using sh-mode lisa-asket
2021-07-04 13:54 ` Lars Ingebrigtsen
2021-07-04 17:18   ` lisa-asket [this message]
2021-07-04 18:38     ` lisa-asket
2021-08-10 15:52       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea-mime-60e1ed50-6a61-1890c5ee@www-8.mailo.com \
    --to=lisa-asket@perso.be \
    --cc=49346@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).