* bug#12682: 24.2.50; make server-execute less noisy @ 2012-10-19 13:09 Christopher Schmidt 2012-10-19 16:46 ` Glenn Morris 0 siblings, 1 reply; 6+ messages in thread From: Christopher Schmidt @ 2012-10-19 13:09 UTC (permalink / raw) To: 12682 severity: wishlist In server-execute, there is this form: (message "%s" (substitute-command-keys "When done with this frame, type \\[delete-frame]")) It would be great if one could disable this messages. Christopher ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#12682: 24.2.50; make server-execute less noisy 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 0 siblings, 1 reply; 6+ messages in thread From: Glenn Morris @ 2012-10-19 16:46 UTC (permalink / raw) To: 12682 Christopher Schmidt wrote: > In server-execute, there is this form: > > (message "%s" (substitute-command-keys > "When done with this frame, type \\[delete-frame]")) > > It would be great if one could disable this messages. Maybe it could respect emacsclient's --quiet option? ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#12682: 24.2.50; make server-execute less noisy 2012-10-19 16:46 ` Glenn Morris @ 2012-10-19 23:28 ` Juanma Barranquero 2012-10-21 19:55 ` Christopher Schmidt 2021-09-06 11:01 ` Lars Ingebrigtsen 0 siblings, 2 replies; 6+ messages in thread From: Juanma Barranquero @ 2012-10-19 23:28 UTC (permalink / raw) To: Glenn Morris; +Cc: 12682 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). This is a wontfix IMO. Juanma ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#12682: 24.2.50; make server-execute less noisy 2012-10-19 23:28 ` Juanma Barranquero @ 2012-10-21 19:55 ` Christopher Schmidt 2012-10-21 23:33 ` Juanma Barranquero 2021-09-06 11:01 ` Lars Ingebrigtsen 1 sibling, 1 reply; 6+ messages in thread From: Christopher Schmidt @ 2012-10-21 19:55 UTC (permalink / raw) To: 12682 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#12682: 24.2.50; make server-execute less noisy 2012-10-21 19:55 ` Christopher Schmidt @ 2012-10-21 23:33 ` Juanma Barranquero 0 siblings, 0 replies; 6+ messages in thread From: Juanma Barranquero @ 2012-10-21 23:33 UTC (permalink / raw) To: 12682 On Sun, Oct 21, 2012 at 9:55 PM, Christopher Schmidt <christopher@ch.ristopher.com> wrote: > There are other, useful messages in server-execute. A more > sophisticated advice is not trivial any more. Not very hard, anyway. > 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. Fair enough. > 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 suppose "superfluous" is in the eye of the beholder. I find the C-x # message a useful reminder (because I really rarely use emacsclient without --no-wait), and it seems like a newbie-oriented message anyway. > ...I am fine with wontfix. I haven't tagged it as wontfix, just stating my opinion. Someone is bound to differ, I suppose. > 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. I think both messages and warnings should have a customizable way to filter them out (with several criteria, from the very text of the message/warning to categories, etc). For warnings that already exists through the severity level, though it is pretty coarse. Juanma ^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#12682: 24.2.50; make server-execute less noisy 2012-10-19 23:28 ` Juanma Barranquero 2012-10-21 19:55 ` Christopher Schmidt @ 2021-09-06 11:01 ` Lars Ingebrigtsen 1 sibling, 0 replies; 6+ messages in thread From: Lars Ingebrigtsen @ 2021-09-06 11:01 UTC (permalink / raw) To: Juanma Barranquero; +Cc: 12682, Glenn Morris Juanma Barranquero <lekktu@gmail.com> writes: > 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)) We now have `set-message-function', which can be used by the user to filter out messages that the user doesn't like. > 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). > > This is a wontfix IMO. So I'm closing this bug report. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-09-06 11:01 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2012-10-21 23:33 ` Juanma Barranquero 2021-09-06 11:01 ` Lars Ingebrigtsen
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).