From: Bartosz Duszel <dptdescribe@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10945@debbugs.gnu.org
Subject: bug#10945: Can't search through help menu.
Date: Thu, 4 May 2017 17:54:10 +0200 [thread overview]
Message-ID: <A981880E-E072-48EA-9C3C-7A78DD16545E@gmail.com> (raw)
In-Reply-To: <0d03e4b4-a581-4137-994f-42f45f506f72@default>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
> On 4 May 2017, at 17:52, Drew Adams <drew.adams@oracle.com> wrote:
>
>> This one is pretty old but I wonder - is it a bug or not? Should we allow to
>> enter window with help?
>
> No idea what this means. Maybe it's clear to someone else; dunno.
>
> Could you give a recipe to describe what you cannot do that you
> would like to do? Start with what it is that you mean by "help
> menu" - do you mean the menu-bar menu `Help'? If so, what do you
> mean by "search through" such a menu?
Hmmm… I thought that if reply to this bug number it will somehow present the thread history.
Anyway - here is the bug report:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10945 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10945>
[-- Attachment #2: Type: text/html, Size: 1471 bytes --]
next prev parent reply other threads:[~2017-05-04 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 10:07 bug#10945: Can't search through help menu Alan Mackenzie
2017-05-04 15:43 ` Bartosz Duszel
2017-05-04 15:52 ` Drew Adams
2017-05-04 15:54 ` Bartosz Duszel [this message]
2017-05-04 15:57 ` Drew Adams
2017-05-04 16:05 ` Drew Adams
2017-05-04 16:59 ` Bartosz Duszel
2017-05-04 18:10 ` Bartosz Duszel
2017-05-05 2:48 ` npostavs
2017-05-05 3:40 ` Drew Adams
2017-05-05 12:12 ` npostavs
2019-11-01 22:24 ` Stefan Kangas
2019-11-13 20:56 ` Juri Linkov
2019-11-14 18:24 ` Alan Mackenzie
2019-11-18 21:18 ` Juri Linkov
2021-10-23 3:49 ` Stefan Kangas
2021-10-23 18:23 ` Juri Linkov
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=A981880E-E072-48EA-9C3C-7A78DD16545E@gmail.com \
--to=dptdescribe@gmail.com \
--cc=10945@debbugs.gnu.org \
--cc=drew.adams@oracle.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.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).