From: Christopher Schmidt <christopher@ch.ristopher.com>
To: 12682@debbugs.gnu.org
Subject: bug#12682: 24.2.50; make server-execute less noisy
Date: Sun, 21 Oct 2012 20:55:33 +0100 (BST) [thread overview]
Message-ID: <87objv7g7g@ch.ristopher.com> (raw)
In-Reply-To: <CAAeL0SToyaOZFX_ajPpmpLXjVuQeQvqDHgj5k_oOKWXv-NivFQ@mail.gmail.com> (Juanma Barranquero's message of "Sat, 20 Oct 2012 01:28:35 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Fri, Oct 19, 2012 at 6:46 PM, Glenn Morris <rgm@gnu.org> wrote:
>
>> Maybe it could respect emacsclient's --quiet option?
>
> I don't think it's a good match. And Christopher likely wants to
> silence the message in all situations.
>
> The fact is that many Emacs functions show messages and we don't add
> options to disable them. In this case it is trivial to add an advice
> in his own's .emacs:
>
> (defadvice server-execute (around silence-server-execute activate compile)
> (with-temp-message ""
> ad-do-it))
>
> and the messages still get logged on *Messages* in case there's
> something else going on (or the advice can be more sofisticate and
> check *Messages* to be sure than nothing untold is happening).
There are other, useful messages in server-execute. A more
sophisticated advice is not trivial any more. server-execute is an
internal, undocumented function. The message may be subject to change,
the form might be refactored to another function in future versions. I
would like to have a permanent solution.
There are many superfluous messages floating around, making my
*Messages*-buffer a pain to look at and my minibuffer a constant source
of distraction. I will not create feature requests for all these
messages. Right now, to me, it is just about this one and the one I
reported in bug 12370 because IMO these two provide absolutely no value
whatsoever. I am fine with "Mark set", "Starting new Ispell process",
"Quit", etc. - but Emacs telling me the keys of its most fundamental
commands - all the time, all over again!? I do not like that.
Having that said...
> This is a wontfix IMO.
...I am fine with wontfix.
I guess a real solution to the underlying problem would be to attach a
log-level or a category-symbol to each message, with the user being able
to disable certain categories. I do realise this is quiet a demand and
there are lots of more important things to implement.
Christopher
next prev parent reply other threads:[~2012-10-21 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 13:09 bug#12682: 24.2.50; make server-execute less noisy Christopher Schmidt
2012-10-19 16:46 ` Glenn Morris
2012-10-19 23:28 ` Juanma Barranquero
2012-10-21 19:55 ` Christopher Schmidt [this message]
2012-10-21 23:33 ` Juanma Barranquero
2021-09-06 11:01 ` Lars Ingebrigtsen
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=87objv7g7g@ch.ristopher.com \
--to=christopher@ch.ristopher.com \
--cc=12682@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.