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: Thu, 13 Apr 2023 15:49:35 +0000 [thread overview]
Message-ID: <874jpj7pf4.fsf@localhost> (raw)
In-Reply-To: <CAM9ALR_eThTGvZifi3jbyQxBBnVXchFOJzWg+sEiQJcwk0-vGA@mail.gmail.com>
Gustavo Barros <gusbrs.2016@gmail.com> writes:
> I get that. But please look at it from my perspective too. This is a
> reiteration of a previous report. Now you are asking me to make a
> third one, which would have to start from scratch.
Not from scratch, if you link this discussion.
> Also, if Emacs devs are requested to chime in by Org devs it is
> different from "just another user's report". Besides, I don't even
> understand why you say this is an Emacs problem, so I'd be at a loss
> at even trying to explain what the general problem is.
I suspect that it might be Emacs problem.
It will be enough for you to mention that I asked you to report to Emacs
bug tracker.
--
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:[~2023-04-13 15:48 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jpj7pf4.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 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.