From: Daniel Pfeiffer <occitan@esperanto.org>
Cc: emacs-devel@gnu.org
Subject: Re: Font lock bug in sh-script.el
Date: Mon, 16 Dec 2002 08:53:50 +0100 [thread overview]
Message-ID: <20021216085350.5a31b585.occitan@esperanto.org> (raw)
In-Reply-To: <E18NiMK-0006j9-00@fencepost.gnu.org>
Hi Richard,
Richard Stallman <rms@gnu.org> skribis:
> This shell script
> svrmgrl << EOF
> CONNECT INTERNAL
> STARTUP
> EXIT
> EOF
>
> while
> # foo
> seems to confuse sh-script.el's font lock support.
> All the text following the first line is treated as a here-document.
That is correct! Only in the first column does EOF have it's special meaning.
> Note that all the spaces in this test case are ordinary spaces.
> (Someone else reported a bug involving non-breaking spaces.)
Yes, he sent it to me first, and I asked him to send it to the bug list, since I no longer use shell (Perl instead :-).
Anyways, those non-breaking spaces are pretty whacky. While they work in both bash and pdksh, neither documents what that EOF may look like. The bash manual calls it a word, so accepting nbsp`s here is almost a bash bug.
As long as there is no specification, all you could do is trial and error, to find the common subset of characters accepted by all shells, or differentiate for each one. In the latter case I guess you'd be fighting with differences between various commercial ksh`s...
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
-- GPL 3: take the wind out of Palladium's sails! --
------
-- My other stuff here too, sawfish, make.pl...: --
------
-- http://dapfy.bei.t-online.de/ --
next prev parent reply other threads:[~2002-12-16 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 23:39 Font lock bug in sh-script.el Richard Stallman
2002-12-16 7:53 ` Daniel Pfeiffer [this message]
2002-12-16 14:08 ` Stefan Monnier
2002-12-16 16:56 ` Stefan Monnier
2002-12-17 18:44 ` Richard Stallman
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=20021216085350.5a31b585.occitan@esperanto.org \
--to=occitan@esperanto.org \
--cc=emacs-devel@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.