unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, 62847@debbugs.gnu.org
Subject: bug#62847: 29.0.90; Propertized space in Org Agenda's mode-name
Date: Sat, 15 Apr 2023 08:28:28 -0300	[thread overview]
Message-ID: <CAM9ALR_k-vmG9tHja1gLoD-uDXOqs-fAdJcbsN-E99t+9=kT_w@mail.gmail.com> (raw)
In-Reply-To: <83o7npct3x.fsf@gnu.org>

Hi Eli,

thanks for looking into this.

On Sat, 15 Apr 2023 at 07:55, Eli Zaretskii <eliz@gnu.org> wrote:

> So this sounds like some weird heisenbug.

I'm not sure it helps much, but I do have a functioning workaround,
which doesn't do much but may offer some hint on the source of the
problem. It basically "replaces" the space with a space in `mode-name`
with an `:after` advice:

    (defun gb/org-agenda-set-mode-name-advice ()
      (let ((before (butlast mode-name
                             (length (member " " mode-name))))
            (after (cdr (member " " mode-name))))
        (when (= (length before) 2)
          (setq mode-name (append before (list " ") after))
          (force-mode-line-update))))
    (advice-add 'org-agenda-set-mode-name
                :after #'gb/org-agenda-set-mode-name-advice)

I don't know why the space set in my init file is different from the
one set in `org-agenda.el`. But Ihor's insight that the problem only
happens on an installed version suggests a compilation related issue,
as he says.

Best,
Gustavo.





  reply	other threads:[~2023-04-15 11:28 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
2023-04-15 10:40         ` Ihor Radchenko
2023-04-15 10:55           ` Eli Zaretskii
2023-04-15 11:28             ` Gustavo Barros [this message]
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='CAM9ALR_k-vmG9tHja1gLoD-uDXOqs-fAdJcbsN-E99t+9=kT_w@mail.gmail.com' \
    --to=gusbrs.2016@gmail.com \
    --cc=62847@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).