unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
Cc: 44592@debbugs.gnu.org
Subject: bug#44592: In sh-script-mode, should the syntax of . and / be made symbol?
Date: Sat, 14 Nov 2020 17:44:17 +0100	[thread overview]
Message-ID: <87eekvyjku.fsf@gnus.org> (raw)
In-Reply-To: <fv2zojo8k2y9ar.fsf@gmail.com> (Dario Gjorgjevski's message of "Thu, 12 Nov 2020 14:49:32 +0100")

Dario Gjorgjevski <dario.gjorgjevski@gmail.com> writes:

> 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.

I think that sounds like a too drastic change in how the mode works,
perhaps -- how the killing commands (etc) works gets into your muscle
memory.

> What do you think?  Alternatively, we could work on fixing only the
> SMIE-provided indentation and leave the syntax as it is.

I think that sounds like a better solution.

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





  reply	other threads:[~2020-11-14 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 13:49 bug#44592: In sh-script-mode, should the syntax of . and / be made symbol? Dario Gjorgjevski
2020-11-14 16:44 ` Lars Ingebrigtsen [this message]
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

  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=87eekvyjku.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44592@debbugs.gnu.org \
    --cc=dario.gjorgjevski@gmail.com \
    /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).