From: Noam Postavsky <npostavs@gmail.com>
To: gyliamos@gmail.com
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Making a non-ASCII space character visible
Date: Mon, 18 Jun 2018 21:01:48 -0400 [thread overview]
Message-ID: <CAM-tV--rTXpKVD9UzVsabyDJT=D3kqiJTdgqJvHrMuerV-NXvg@mail.gmail.com> (raw)
In-Reply-To: <for20tFao41U2@mid.individual.net>
On 18 June 2018 at 20:45, Will Parsons <varro@nodomain.invalid> wrote:
>> Reported as bug#31869.
>
> While I'm glad that I've helped to identify a bug in Emacs, I'm
> curious on how I should be able to track the progress of the bug
> report. Doing a search on (e.g.) "emacs bug 31869" seems to result in
> no useful results.
You can find the report at https://debbugs.gnu.org/31869
There's unfortunately no great way of tracking it (that is, receiving
notifications about changes) at the moment apart from subscribing to
the bug list as a whole.
https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
next prev parent reply other threads:[~2018-06-19 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 20:15 Making a non-ASCII space character visible Will Parsons
2018-06-16 21:37 ` Will Parsons
2018-06-17 4:31 ` Marcin Borkowski
2018-06-17 5:07 ` Michael Heerdegen
2018-06-17 5:55 ` Eli Zaretskii
2018-06-17 6:24 ` Michael Heerdegen
2018-06-17 6:41 ` Eli Zaretskii
2018-06-17 6:41 ` Michael Heerdegen
[not found] ` <mailman.2115.1529217694.1292.help-gnu-emacs@gnu.org>
2018-06-19 0:45 ` Will Parsons
2018-06-19 1:01 ` Noam Postavsky [this message]
[not found] ` <mailman.2220.1529370113.1292.help-gnu-emacs@gnu.org>
2018-06-19 1:26 ` Will Parsons
[not found] ` <mailman.2110.1529214934.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:54 ` Will Parsons
2018-06-17 6:00 ` Eli Zaretskii
[not found] ` <mailman.2111.1529215267.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:38 ` Will Parsons
2018-06-17 18:51 ` Eli Zaretskii
[not found] ` <mailman.2145.1529261474.1292.help-gnu-emacs@gnu.org>
2018-06-17 19:09 ` Will Parsons
2018-06-17 19:31 ` Eli Zaretskii
[not found] ` <mailman.2147.1529263896.1292.help-gnu-emacs@gnu.org>
2018-06-17 20:28 ` Will Parsons
2018-06-18 1:40 ` Nick Helm
[not found] ` <mailman.2154.1529286048.1292.help-gnu-emacs@gnu.org>
2018-06-19 0:12 ` Will Parsons
2018-06-19 2:30 ` Nick Helm
[not found] ` <mailman.2227.1529375463.1292.help-gnu-emacs@gnu.org>
2018-06-20 21:05 ` Will Parsons
[not found] ` <mailman.2107.1529212061.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:45 ` Will Parsons
[not found] <<fol9fvF7uauU1@mid.individual.net>
[not found] ` <<fole90F986vU1@mid.individual.net>
2018-06-17 0:20 ` Drew Adams
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='CAM-tV--rTXpKVD9UzVsabyDJT=D3kqiJTdgqJvHrMuerV-NXvg@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=gyliamos@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.