unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: david.ronis@mcgill.ca
Cc: 4134@emacsbugs.donarmstrong.com
Subject: bug#4134: 23.1; Buffer Tab not being linked properly
Date: Thu, 20 Aug 2009 20:34:28 -0400	[thread overview]
Message-ID: <ux8whe3syz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <200908121755.n7CHtfXm023297@ronispc.chem.mcgill.ca> (David Ronis's message of "Wed, 12 Aug 2009 13:55:41 -0400")

tags 4134 moreinfo unreproducible
stop

David Ronis wrote:

> I'm working on a fortran project and am currently using emacs to
> edit the Makefile, fortran source file and to do the compilation
> (I'm also using it to send this bug report). The menubar at the top
> has entries that change when I switch buffers/modes; e.g., right now
> I see entries like
>
> File Edit Options Buffers Tools Headers Mail Mailcrypt Help
>
> Clicking on Mail or Mailcrypt doen't popup a menu.
>
> Switching to my fortran buffer, I have
>
>
> File Edit Options Buffers Tools Fortran Help
>
> Now clicking on Fortran generates the correct menu.
>
> Compiling the program results in a compilation buffer with 
> a menubar containing
>
> File Edit Options Buffers Tools Compile Help
>
> Clicking on Compile gets the Fortran menu.  


I cannot reproduce this. Can you explain how to get to this state,
starting from emacs -Q? For example, Mailcrypt is not part of Emacs.


> In GNU Emacs 23.1.1 (i686-pc-linux-gnu, GTK+ Version 2.12.12)
>  of 2009-07-30 on ronispc
[...]
> configured using `configure 'CC=/usr/bin/gcc' 'CFLAGS=-march=native
> -msse2 -mfpmath=sse -O3 -ffast-math -funroll-loops
> -fomit-frame-pointer -floop-interchange -floop-strip-mine
> -floop-block''

Wow, your Emacs goes to 11.





  reply	other threads:[~2009-08-21  0:34 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 [this message]
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
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=ux8whe3syz.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=4134@emacsbugs.donarmstrong.com \
    --cc=david.ronis@mcgill.ca \
    /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).