From: Ihor Radchenko <yantar92@posteo.net>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)]
Date: Sat, 22 Oct 2022 07:15:06 +0000 [thread overview]
Message-ID: <87h6zw1g91.fsf@localhost> (raw)
In-Reply-To: <878rtv9kx6.fsf@gmail.com>
Gustavo Barros <gusbrs.2016@gmail.com> writes:
> A recipe for it. Start `emacs -Q'. Set things up:
>
> #+begin_src emacs-lisp
> (setq org-agenda-files '("~/agenda.org"))
> (setq eval-expression-print-level nil)
> (setq eval-expression-print-length nil)
> #+end_src
>
> Let's say =agenda.org= contains:
>
> #+begin_src org
> ,* TODO Task
> SCHEDULED: <2022-02-28 Mon>
> #+end_src
>
> 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 (todo-state #("TODO" 0 4 (fontified nil
> ...
> So, it appears that the Org Agenda buffer's properties are somehow
> getting to that particular space in `mode-name'. It completely beats me
> how it is so but, alas, it is there.
I am unable to reproduce with the latest Org.
--
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>
next prev parent reply other threads:[~2022-10-22 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:26 [BUG] Propertized space in Agenda's mode-name [9.5.2 (release_9.5.2-3-geb9f34 @ /usr/local/share/emacs/28.0.91/lisp/org/)] Gustavo Barros
2022-10-22 7:15 ` Ihor Radchenko [this message]
2022-10-22 10:51 ` Gustavo Barros
2023-04-13 13:03 ` Gustavo Barros
2023-04-13 14:26 ` Ihor Radchenko
2023-04-13 14:30 ` Gustavo Barros
2023-04-13 14:55 ` Ihor Radchenko
2023-04-13 15:07 ` Gustavo Barros
2023-04-13 15:13 ` Ihor Radchenko
2023-04-13 15:22 ` Gustavo Barros
2023-04-13 15:49 ` Ihor Radchenko
2023-04-14 23:07 ` Gustavo Barros
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6zw1g91.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).