From: David Ronis <ronis@ronispc.chem.mcgill.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 4134@emacsbugs.donarmstrong.com
Subject: bug#4134: 23.1; Buffer Tab not being linked properly
Date: Thu, 20 Aug 2009 21:31:07 -0400 [thread overview]
Message-ID: <1250818267.2051.4.camel@montroll.chem.mcgill.ca> (raw)
In-Reply-To: <h0ws4yhsle.fsf@fencepost.gnu.org>
On Thu, 2009-08-20 at 21:18 -0400, Glenn Morris wrote:
> David Ronis wrote:
>
> > 1. started 'emacs -Q model.f' as suggested.
> > 2. emacs sets the buffer mode to fortran and I have the usual "Fortran"
> > button in the menubar.
> > 3. compile the program using alt-x compile (then simply run make without
> > -k). The window splits and I see the expected output of the
> > compilation.
> >
> > If I set the focus to the *compile* buffer, the "Fortran" menubar button
> > changes to "Compile" (as it should); however, clicking on that button
> > gets the fortran menu, not the compile one.
>
> Sorry, but for me this works as it should.
>
> Are you somehow changing the focus when you go to select the menu bar?
> What happens if you put the compilation window above the Fortran window?
I tried putting the fortran window above, below, and single-window--no
differences.
> > P.S., I've been using emacs for a long time, but where do you see
> > version 11?
>
> I was making fun of your CFLAGS setting. Does that really make any
> measurable difference to anything, or is it just one louder?
Ahh... I leave CFLAGS set to ultra aggressive in the environment (it
does make a difference in some of the things I do, although, very very
very unlikely to be seen in emacs). I'm using gcc 4.4.1 which is
relatively new; perhaps this is a compiler bug. I'll rebuild with saner
flags and see what happens. I'll report back shortly.
Thanks for looking at this.
next prev parent reply other threads:[~2009-08-21 1:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 7:11 bug#4122: Link to corresponding Ubuntu bug era eriksson
2009-09-01 7:15 ` Processed: " Emacs bug Tracking System
2009-09-02 17:04 ` bug#4122: Jan Djärv
2009-08-11 15:31 ` bug#4122: 23.1; GTK menu contents don't change Robin Green
2009-09-02 17:10 ` bug#4122: marked as done (23.1; GTK menu contents don't change) Emacs bug Tracking System
2009-08-11 15:54 ` bug#4125: 23.1; GTK menu contents don't change Robin Green
2009-09-02 17:10 ` bug#4125: marked as done (23.1; GTK menu contents don't change) Emacs bug Tracking System
2009-08-12 17:55 ` bug#4134: 23.1; Buffer Tab not being linked properly David Ronis
2009-08-21 0:34 ` Glenn Morris
2009-08-21 0:40 ` Processed: " Emacs bug Tracking System
2009-08-21 1:00 ` David Ronis
2009-08-21 1:18 ` Glenn Morris
2009-08-21 1:31 ` David Ronis [this message]
2009-08-21 1:51 ` David Ronis
2009-08-21 2:21 ` David Ronis
2009-08-22 23:06 ` Glenn Morris
2009-09-02 17:10 ` bug#4134: marked as done (23.1; Problems with gtk+ >= 2.7.19) Emacs bug Tracking System
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=1250818267.2051.4.camel@montroll.chem.mcgill.ca \
--to=ronis@ronispc.chem.mcgill.ca \
--cc=4134@emacsbugs.donarmstrong.com \
--cc=rgm@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 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).