From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 4147@debbugs.gnu.org
Subject: bug#4147: 23.1.50: Info-search command strange behaviour
Date: Mon, 21 Dec 2009 09:21:46 +0100 [thread overview]
Message-ID: <4B2F301A.8010208@gmx.at> (raw)
In-Reply-To: <878wcxp349.fsf@mail.jurta.org>
> The toolbar is represented by a propertized string created by
> `build_desired_tool_bar_string'. It is only the frame parameter
> `tool_bar_window' that mandates one toolbar per frame.
The one toolbar per frame concept is built into most toolbar handling
routines like note_tool_bar_highlight and some "if drawing a tool-bar
window, draw it over the internal border at the top of the window" stuff
I don't understand completely yet. All these look fairly trivial though
at first glance.
martin
next prev parent reply other threads:[~2009-12-21 8:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 3:49 bug#4147: 23.1.50: Info-search command strange behaviour Jamie Lokier
2009-08-15 10:10 ` martin rudalics
2009-12-05 0:48 ` Juri Linkov
2009-12-05 19:50 ` Juri Linkov
2009-12-08 20:12 ` Juri Linkov
2009-12-14 21:54 ` Juri Linkov
2009-12-14 23:00 ` martin rudalics
2009-12-14 23:56 ` Juri Linkov
2009-12-15 8:16 ` martin rudalics
2009-12-16 0:45 ` Juri Linkov
2009-12-16 7:53 ` martin rudalics
2009-12-16 9:17 ` Juri Linkov
2009-12-16 15:04 ` martin rudalics
2009-12-16 19:21 ` Drew Adams
[not found] ` <87my1ibip3.fsf@mail.jurta.org>
[not found] ` <4B29E99D.9060501@gmx.at>
2009-12-17 23:34 ` Juri Linkov
[not found] ` <4B2B318A.7010300@gmx.at>
2009-12-19 0:30 ` Juri Linkov
2009-12-19 9:09 ` martin rudalics
2009-12-21 0:34 ` Juri Linkov
2009-12-21 8:21 ` martin rudalics [this message]
2009-12-19 0:45 ` Juri Linkov
2009-12-19 9:09 ` martin rudalics
2009-12-21 0:36 ` Juri Linkov
2009-12-21 8:21 ` martin rudalics
2009-12-15 4:07 ` Eli Zaretskii
2011-10-06 3:41 ` Glenn Morris
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=4B2F301A.8010208@gmx.at \
--to=rudalics@gmx.at \
--cc=4147@debbugs.gnu.org \
--cc=juri@jurta.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 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).