unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Emanuel Berg <incal@dataswamp.org>, help-gnu-emacs@gnu.org
Subject: Re: Allowing spaces in the regexp for outlines
Date: Thu, 21 Mar 2024 06:40:56 +0000	[thread overview]
Message-ID: <dNVB4H-uNKLeU-kwvPjjYZNQ2LrYT05Xg3k9C3UDvX0UUXebvqk4xG_rfM5n6BXtfBOWjkQwayqCySY6XEVTrGE7_FNpjBTGhiEpYfPqnzw=@protonmail.com> (raw)
In-Reply-To: <GPwew4Yl96rwPSUZPVSrO3d44T2bhybkR17Rw7YFlgSnfxY2cz5-mUenNWc29sEzbX7x5f3ysMXzXy7g1qSlrS_LVHoycqevC-B_c_w7sQk=@protonmail.com>


On Thursday, March 21st, 2024 at 5:08 PM, Heime <heimeborgia@protonmail.com> wrote:

> On Thursday, March 21st, 2024 at 7:45 AM, Emanuel Berg incal@dataswamp.org wrote:
> 
> > Heime wrote:
> > 
> > > (defvar el-hglevels
> > > '( (";;; H1" . 1) (";;; H2" . 2) (";;; H3" . 3) (";;; H4" . 4) )
> > > "Outline levels for elisp major mode.")
> > 
> > You can also use `comment-start' instead of hardcoding ';',
> > and use explicit repitition instead of hardcoding 3 - see
> > 
> > (info "(elisp) Regexp Backslash")
> > 
> > - and then also not hardcode the 1s, 2s, 3s, and 4s in pairs
> > but inserting them as integers into the string.
> > 
> > So yes, you can improve a lot! And spend all weekend on it.
> 
> 
> Have attempted the following without success
> 
> (";;;\\[[:space:]]+H1" . 1)
> 
> (";;;\[[:space:]]+H1" . 1)
> 
> (";;;[[:space:]]+H1" . 1)

And now as well with

(";;;\\([[:space:]]+\\)H1" . 1)




  reply	other threads:[~2024-03-21  6:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 19:24 Allowing spaces in the regexp for outlines Heime
2024-03-20 19:45 ` Emanuel Berg
2024-03-21  4:44   ` Heime
2024-03-21  4:59     ` Emanuel Berg
2024-03-21  5:08   ` Heime
2024-03-21  6:40     ` Heime [this message]
2024-03-21 19:52       ` Emanuel Berg
2024-03-21  4:32 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-03-21  4:49   ` Emanuel Berg
2024-03-22 12:56     ` Arash Esbati
2024-03-22 15:39       ` Heime
2024-03-27 19:12   ` Christopher Dimech
2024-03-27 19:32     ` Heime

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='dNVB4H-uNKLeU-kwvPjjYZNQ2LrYT05Xg3k9C3UDvX0UUXebvqk4xG_rfM5n6BXtfBOWjkQwayqCySY6XEVTrGE7_FNpjBTGhiEpYfPqnzw=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.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.
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).