From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 62847@debbugs.gnu.org, gusbrs.2016@gmail.com
Subject: bug#62847: 29.0.90; Propertized space in Org Agenda's mode-name
Date: Sat, 15 Apr 2023 13:24:05 +0300 [thread overview]
Message-ID: <83sfd1cuka.fsf@gnu.org> (raw)
In-Reply-To: <875y9xlayt.fsf@localhost> (message from Ihor Radchenko on Sat, 15 Apr 2023 10:02:34 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: gusbrs.2016@gmail.com, 62847@debbugs.gnu.org
> Date: Sat, 15 Apr 2023 10:02:34 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I'm afraid I don't understand this bug report, and cannot reproduce
> > what I thought I understood from it. Any chance of presenting a
> > recipe starting from "emacs -Q", for someone who doesn't use
> > org-agenda?
>
> 1. emacs -Q
> 2. Create and open a new Org file with the following contents:
>
> * TODO Task
> SCHEDULED: <2023-04-14 Fri>
>
> 3. M-x org-agenda <RET> < a
> 4. M-: mode-name <RET>
> 5. Observe the third element (" ") in the list propertized unexpectedly,
> despite `org-agenda-set-mode-name' using " " without properties.
Thanks, but it isn't propertized here, I see a literal " " with no
properties.
What happens if you display mode-name inside org-agenda-set-mode-name:
does it have the properties there already?
next prev parent reply other threads:[~2023-04-15 10:24 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
2023-04-15 9:49 ` Eli Zaretskii
2023-04-15 10:02 ` Ihor Radchenko
2023-04-15 10:24 ` Eli Zaretskii [this message]
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
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=83sfd1cuka.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62847@debbugs.gnu.org \
--cc=gusbrs.2016@gmail.com \
--cc=yantar92@posteo.net \
/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 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).