unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: restrictive/discrete messages log (was: Re: Suppress (pop kill-ring) from *Messages*)
Date: Mon, 02 Nov 2015 02:05:12 +0100	[thread overview]
Message-ID: <8737wp2otz.fsf@debian.uxu> (raw)
In-Reply-To: 20151101195356.GD3304@mail.akwebsoft.com

Tim Johnson <tim@akwebsoft.com> writes:

> How can I suppress the recording of the item
> in messages?

How can one do this in general?

For the debugger, there is, for example

    ;; ignore a couple of common "errors"
    (setq debug-ignored-errors
          '(quit
            beginning-of-line    end-of-line
            beginning-of-buffer  end-of-buffer
            end-of-file
            buffer-read-only
            file-supersession) )

but for messages? The only thing I can think of is
the command that brings up the messages buffer.
Then you can do some filtering, like this:

    (defun switch-to-filtered-messages-buffer ()
      (interactive)
      (switch-to-buffer (messages-buffer))
      (let ((inhibit-read-only t))
        (goto-char 0)
        (while (re-search-forward "Mark set\n" nil t) ; no BOUND; NOERROR
          (replace-match "") ))
      (goto-char (point-max)) )

However, it doesn't work if the messages buffer is
visible already and the user doesn't have to invoke
a command to bring it up.

You see? Yet another advantage for the two-pane, tty
solution where buffers constantly have to be "brought
up"! :)

-- 
underground experts united
http://user.it.uu.se/~embe8573




      parent reply	other threads:[~2015-11-02  1:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 19:53 Suppress (pop kill-ring) from *Messages* Tim Johnson
2015-11-01 21:19 ` Random832
2015-11-01 21:19 ` Random832
2015-11-01 21:33 ` Marcin Borkowski
2015-11-01 21:55   ` Tim Johnson
2015-11-02  0:41 ` Emanuel Berg
2015-11-02 16:23   ` Tim Johnson
2015-11-03  2:46     ` Emanuel Berg
2015-11-02  1:05 ` Emanuel Berg [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737wp2otz.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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.
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).