From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: quoting Emacs Lisp
Date: Mon, 24 Jan 2011 13:47:27 -0800 [thread overview]
Message-ID: <874o8yq8i8.fsf@gnus.org> (raw)
In-Reply-To: <87pqrmchqz.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> I can push a fix into the Emacs trunk. Looks like just `sh-set-sell'
> needs a fix for this issue; I can add a `sh-verbose' variable you can
> override. `message' is used unconditionally a LOT in that code but I
> don't think it's necessary to make it all dependent on `sh-verbose'.
Sounds good. Or perhaps all the messages in sh-set-shell should just be
removed. Do you really need to know "Indentation setup for shell type
bash" every time you open a shell script?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-24 21:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 10:42 Problem displaying multipart/alternative messages Michael Piotrowski
2011-01-20 14:21 ` Michael Piotrowski
2011-01-20 17:55 ` Julien Danjou
2011-01-20 20:56 ` quoting Emacs Lisp (was: Problem displaying multipart/alternative messages) Ted Zlatanov
2011-01-20 21:05 ` quoting Emacs Lisp Julien Danjou
2011-01-20 21:17 ` Ted Zlatanov
2011-01-20 21:31 ` Julien Danjou
2011-01-20 21:36 ` Julien Danjou
2011-01-24 1:00 ` Lars Ingebrigtsen
2011-01-24 10:29 ` Julien Danjou
2011-01-24 17:51 ` Ted Zlatanov
2011-01-24 21:47 ` Lars Ingebrigtsen [this message]
2011-01-24 22:09 ` Ted Zlatanov
2011-01-24 22:26 ` Daniel Pfeiffer
2011-01-25 10:18 ` Julien Danjou
2011-01-22 4:50 ` Lars Ingebrigtsen
2011-01-24 1:06 ` Problem displaying multipart/alternative messages Lars Ingebrigtsen
2011-01-22 4:48 ` Lars Ingebrigtsen
2011-01-22 8:06 ` Julien Danjou
2011-01-22 19:50 ` Eric S Fraga
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=874o8yq8i8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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 NNTP newsgroup(s).