From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: ruijie@netyu.xyz, senkijun@gmail.com, 64652@debbugs.gnu.org
Subject: bug#64652: 28.2; Adding a property bug on Windows 11
Date: Sat, 15 Jul 2023 21:53:26 +0300 [thread overview]
Message-ID: <83ilalatw9.fsf@gnu.org> (raw)
In-Reply-To: <871qh9t7of.fsf@localhost> (message from Ihor Radchenko on Sat, 15 Jul 2023 17:18:24 +0000)
> Cc: Senki Jun <senkijun@gmail.com>, 64652@debbugs.gnu.org
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Sat, 15 Jul 2023 17:18:24 +0000
>
> Ruijie Yu <ruijie@netyu.xyz> writes:
>
> > Sounds like an Org bug report (from the keybind C-c C-x P and the term "property drawer"), so I'm taking the liberty of CC'ing Ihor.
>
> Nope. This was originally a question on reddit and I specifically asked
> to report as Emacs bug.
>
> Because the problem is only triggered on Windows, and not on Linux.
Please show a minimal recipe for reproducing the problem starting from
"emacs -Q". Otherwise, I don't see how we can look into this.
next prev parent reply other threads:[~2023-07-15 18:53 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 13:27 bug#64652: 28.2; Adding a property bug on Windows 11 Senki Jun
2023-07-15 17:07 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 17:18 ` Ihor Radchenko
2023-07-15 18:53 ` Eli Zaretskii [this message]
2023-07-15 19:24 ` Senki Jun
2023-07-15 20:09 ` Senki Jun
2023-07-16 5:03 ` Eli Zaretskii
2023-07-16 5:59 ` Ihor Radchenko
2023-07-16 6:16 ` Senki Jun
2023-07-16 6:34 ` Ihor Radchenko
2023-07-16 6:40 ` Senki Jun
2023-07-16 6:44 ` Ihor Radchenko
2023-07-16 6:56 ` Senki Jun
2023-07-16 7:12 ` Senki Jun
2023-07-16 7:15 ` Ihor Radchenko
2023-07-16 7:20 ` Senki Jun
2023-07-16 7:29 ` Eli Zaretskii
2023-07-16 7:31 ` Senki Jun
2023-07-16 7:33 ` Senki Jun
2023-07-16 7:37 ` Ihor Radchenko
2023-07-16 7:52 ` Eli Zaretskii
2023-07-16 8:07 ` Ihor Radchenko
2023-07-16 8:16 ` Senki Jun
2023-07-16 8:40 ` Eli Zaretskii
2023-07-16 8:56 ` Senki Jun
2023-07-16 8:56 ` Ihor Radchenko
2023-07-16 9:03 ` Eli Zaretskii
2023-07-16 9:09 ` Eli Zaretskii
2023-07-16 9:20 ` Ihor Radchenko
2023-07-16 9:21 ` Ihor Radchenko
2023-07-16 10:21 ` Eli Zaretskii
2023-07-16 10:25 ` Ihor Radchenko
2023-07-16 11:07 ` Mattias Engdegård
2023-07-16 11:36 ` Eli Zaretskii
2023-07-16 12:11 ` Ihor Radchenko
2023-07-16 12:59 ` Eli Zaretskii
2023-07-16 13:06 ` Ihor Radchenko
2023-07-16 13:40 ` Eli Zaretskii
2023-07-16 17:16 ` Senki Jun
2023-07-16 9:04 ` Ihor Radchenko
2023-07-16 7:23 ` Eli Zaretskii
2023-07-16 7:26 ` Eli Zaretskii
2023-07-16 7:25 ` Eli Zaretskii
2023-07-16 4:47 ` Eli Zaretskii
[not found] ` <87wmz0mma4.fsf@localhost>
2023-07-16 7:24 ` Eli Zaretskii
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=83ilalatw9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64652@debbugs.gnu.org \
--cc=ruijie@netyu.xyz \
--cc=senkijun@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 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.