all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: 62847@debbugs.gnu.org
Subject: bug#62847: 29.0.90; Propertized space in Org Agenda's mode-name
Date: Sat, 15 Apr 2023 09:38:43 +0000	[thread overview]
Message-ID: <87edollc2k.fsf@localhost> (raw)
In-Reply-To: <CAM9ALR9X_XGN3NUng_2uesOnYHs8r_Q3eBm5AK+cayXCefK5Og@mail.gmail.com>

Gustavo Barros <gusbrs.2016@gmail.com> writes:

> Call `M-x org-agenda RET a'.  Now examine `mode-name' with `M-:
> mode-name RET' to get:
>
> #+begin_src emacs-lisp
> ("Org-Agenda" "" #(" " 0 1 (org-category "agenda" tags nil...

I suspect that it is Emacs-related because I see nothing wrong done on
Org side.

The code setting `mode-name' is

(defun org-agenda-set-mode-name ()
  "Set the mode name to indicate all the small mode settings."
  (setq mode-name
	(list "Org-Agenda"
	      (if (get 'org-agenda-files 'org-restrict) " []" "")
	      " "
	      '(:eval (org-agenda-span-name org-agenda-current-span))
              ...)))

Note the third " " in `mode-name' list.
Org does not modify the mode-name by side effect.

This bug is only reproducible when using built-in Org. When I tried to
reproduce with Git version of Org (the same release tag), no extra
properties are present in `mode-name'.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2023-04-15  9:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 23:04 bug#62847: 29.0.90; Propertized space in Org Agenda's mode-name Gustavo Barros
2023-04-15  9:38 ` Ihor Radchenko [this message]
2023-04-15  9:49   ` Eli Zaretskii
2023-04-15 10:02     ` Ihor Radchenko
2023-04-15 10:24       ` Eli Zaretskii
2023-04-15 10:40         ` Ihor Radchenko
2023-04-15 10:55           ` Eli Zaretskii
2023-04-15 11:28             ` Gustavo Barros
2023-04-15 11:44             ` Ihor Radchenko
2023-04-15 11:49               ` Gustavo Barros
2023-04-15 12:08                 ` Ihor Radchenko
2023-04-15 13:21                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16 11:23                     ` Ihor Radchenko
2023-04-16 11:49                       ` Gustavo Barros
2023-04-15 11:38           ` Eli Zaretskii
2023-04-15 11:44             ` Ihor Radchenko
2023-04-15 11:45               ` Eli Zaretskii
2023-04-15 13:15                 ` Mattias Engdegård
2023-04-16 11:29                   ` Ihor Radchenko
2023-04-16 12:02                     ` Mattias Engdegård
2023-04-16 12:17                       ` Ihor Radchenko
2023-04-16 12:58                         ` Eli Zaretskii
2023-04-16 13:14                           ` Ihor Radchenko
2023-04-16 14:43                             ` Eli Zaretskii
2023-04-16 14:52                               ` Ihor Radchenko
2023-04-16 15:17                                 ` Eli Zaretskii
2023-04-16 14:51                       ` Mattias Engdegård
2023-04-16 14:53                         ` Mattias Engdegård
2023-04-16 12:38 ` Daniel Mendler

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=87edollc2k.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=62847@debbugs.gnu.org \
    --cc=gusbrs.2016@gmail.com \
    /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.