From: Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
To: 44592@debbugs.gnu.org
Subject: bug#44592: In sh-script-mode, should the syntax of . and / be made symbol?
Date: Thu, 12 Nov 2020 14:49:32 +0100 [thread overview]
Message-ID: <fv2zojo8k2y9ar.fsf@gmail.com> (raw)
In the syntax table of sh-script-mode, the syntax of . and / is
punctuation. This has the advantage of being able to use, e.g.,
kill-sexp to kill one component of a path. However, it also has the
disadvantage of not correctly indenting line continuations when a path
to a command is given.
As an example, consider:
relative-path/to/configure --prefix=$prefix \
--with-x \
--with-x-toolkit=gtk3 \
--with-cairo
(This is how I would expect it to be indented.) Currently,
sh-script-mode would consider only relative-path to be the first sexp on
the leading line and therefore indent it as:
relative-path/to/configure --prefix=$prefix \
--with-x \
--with-x-toolkit=gtk3 \
--with-cairo
Changing the syntax of . and / to symbol would make the entire
relative-path/to/configure be considered the first sexp and therefore
give the correct indentation show above.
Moreover, one would then be able to use, e.g., kill-sexp to kill a full
path as opposed to just one component.
What do you think? Alternatively, we could work on fixing only the
SMIE-provided indentation and leave the syntax as it is.
Best regards,
Dario
--
$ keyserver=hkps://hkps.pool.sks-keyservers.net
$ keyid=744A4F0B4F1C9371
$ gpg --keyserver $keyserver --search-keys $keyid
next reply other threads:[~2020-11-12 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 13:49 Dario Gjorgjevski [this message]
2020-11-14 16:44 ` bug#44592: In sh-script-mode, should the syntax of . and / be made symbol? Lars Ingebrigtsen
2020-12-23 16:05 ` Dario Gjorgjevski
2020-12-23 22:24 ` Lars Ingebrigtsen
2020-12-24 3:59 ` Stefan Monnier
2021-08-27 17:09 ` Lars Ingebrigtsen
2021-08-28 9:44 ` Kévin Le Gouguec
2021-08-29 18:29 ` Lars Ingebrigtsen
2021-08-29 21:22 ` Kévin Le Gouguec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fv2zojo8k2y9ar.fsf@gmail.com \
--to=dario.gjorgjevski@gmail.com \
--cc=44592@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.