Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: [change the default registry names] (was: registry seems to be saved for 27.0.50 any longer/Gnorb)
Date: Thu, 26 Apr 2018 18:35:22 +0200	[thread overview]
Message-ID: <87a7tqudrp.fsf_-_@mat.ucm.es> (raw)
In-Reply-To: <87a7tqdmiz.fsf@web.de>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

>>> "Michael" == Michael Heerdegen <michael_heerdegen@web.de> writes:

   > Uwe Brauer <oub@mat.ucm.es> writes:
   >> So everything looks ok now, but I think the registry should be fixed
   >> also by Lars/or the GNU emacs maintainers.

   > It is fixed AFAICT in master (at least it should be, and is for me).
   > But you need to upgrade Emacs.  Note that the necessary changes were in
   > eieio, so updating only some gnus libraries is not enough (dunno what
   > exactly you tried, maybe elaborate).  `gnus-registry-fixit' should only
   > be needed to be called once.

Besides gnorb I also use the registry to add the labels Todo Important
etc, however I find the original names to long, and the chars to short,
so I have
(defalias 'gnus-user-format-function-M
'gnus-registry-article-marks-to-names)

And I tried

(setq gnus-registry-marks nil)

(defvar  gnus-registry-marks
  '((Imp
     :char ?i
     :image "summary_important")
    (Wrk
     :char ?w
     :image "summary_work")
    (Pers
     :char ?p
     :image "summary_personal")
    (To-Do
     :char ?t
     :image "summary_todo")
    (Later
     :char ?l
     :image "summary_later"))

  "List of registry marks and their options.

`gnus-registry-mark-article' will offer symbols from this list
for completion.

Each entry must have a character to be useful for summary mode
line display and for keyboard shortcuts.

Each entry must have an image string to be useful for visual
display.")

But it does not work my setting is not taken. Did anybody try to
configure the names for the gnus registry?

Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

  parent reply	other threads:[~2018-04-26 16:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 12:52 registry seems to be saved for 27.0.50 any longer/Gnorb Uwe Brauer
2018-04-26 13:28 ` Michael Heerdegen
2018-04-26 15:09   ` Uwe Brauer
2018-04-26 15:18     ` Michael Heerdegen
2018-04-26 15:55       ` Uwe Brauer
2018-04-26 16:35       ` Uwe Brauer [this message]
2018-04-26 18:46         ` [change the default registry names] Eric Abrahamsen
2018-04-26 19:19           ` Michael Heerdegen
2018-04-26 19:30             ` Eric Abrahamsen
2018-04-27  9:24           ` Uwe Brauer
2018-04-27 16:59             ` Bob Newell
2018-04-27 18:27               ` Eric Abrahamsen
2018-05-07  8:05               ` Uwe Brauer
2018-05-07 23:43                 ` Bob Newell
2018-05-10  8:11                   ` Uwe Brauer
2018-05-10 12:38                     ` Michael Heerdegen
2018-05-11 17:22                       ` Uwe Brauer
2018-05-11 17:28                         ` Bob Newell
2018-05-07  8:07               ` [setq does not work] (was: [change the default registry names]) Uwe Brauer
2018-04-26 15:15   ` registry seems to be saved for 27.0.50 any longer/Gnorb Uwe Brauer

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=87a7tqudrp.fsf_-_@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).