From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Paul Nienaber <phox@phox.ca>, 3226@debbugs.gnu.org
Subject: bug#3226: here-document syntax inference and completion is broken
Date: Fri, 11 Oct 2019 21:38:11 +0200 [thread overview]
Message-ID: <87eezjm5ss.fsf@gnus.org> (raw)
In-Reply-To: <jwvljpakixl.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Tue, 05 May 2009 23:36:20 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> A default emacs install will complete with "EOF\n\nEOF" (in a more
>> clever fashion so the rest of the line is undisturbed), and place the
>> cursor on the new blank line. This is incorrect behaviour, as it
>> breaks entry of BASH here-strings when the user's intent is
>> still ambiguous.
>
> Thanks for your report. Indeed, sh-mode does not know about
> here-strings at all. I guess waiting for "<<[^<]" is a good idea.
> Patches welcome for Emacs-23.2.
I've now made it look for a space after the << -- that feels more
natural than << and then some arbitrary character. And as far as I can
tell, all the shells handle
foo <<EOF
EOF
and
foo << EOF
EOF
identically.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-11 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 22:15 bug#3226: here-document syntax inference and completion is broken Paul Nienaber
2009-05-06 3:36 ` Stefan Monnier
2019-10-11 19:38 ` Lars Ingebrigtsen [this message]
2019-10-15 22:09 ` Paul Nienaber
2019-10-16 1:40 ` Lars Ingebrigtsen
2019-10-16 6:04 ` Paul Nienaber
2019-10-16 7:20 ` Lars Ingebrigtsen
2019-10-16 12:43 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2009-08-16 14:09 Chong Yidong
2016-01-26 5:15 ` Andrew Hyatt
2016-02-14 14:44 ` Philipp Stephani
2016-03-27 19:56 ` Mark Oteiza
2016-03-27 22:43 ` Stefan Monnier
2016-04-16 18:49 ` Mark Oteiza
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=87eezjm5ss.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=3226@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=phox@phox.ca \
/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.