bug#5878: [Aquamacs-bugs] Re: dired / view buffer / wrong theme (was: no subject)

bug#5878: [Aquamacs-bugs] Re: dired / view buffer / wrong theme (was: no subject)

[David Reitter]

On 6 Jun 2005, at 16:19, Peter Dyballa wrote:

> With C-x d I opened a directory with TeX sources etc. I sorted by  
> time and saw a missfont.log file. I opened it with v, read its  
> contents, and closed it with q. Now the dired buffer is not anymore  
> held in a monospaced font, but in the Lucida Grande default  
> proportional font ...

Good, that has been fixed now; the frame theme is updated to reflect  
the buffer-specific theme now.
(This has been bound to menu-bar-update-hook.)

Thanks for reporting this. [ This was specific to the Aquamacs  
distribution. ]

Dave

bug#5891: [Aquamacs-bugs] Re: (no subject)

[Richard Stallman]

    With C-x d I opened a directory with TeX sources etc. I sorted by time 
    and saw a missfont.log file. I opened it with v, read its contents, 

At this point, if you switch back to the dired buffer, has its font
changed already?

Can you provide us with a complete self-contained test case?
Please read the Bugs section in the Emacs manual, which provides
guidelines on how to write a bug report to give us the
necessary information so we can fix the bug.

bug#5902: [Aquamacs-bugs] Re: (no subject)

[Peter Dyballa]

Am 07.06.2005 um 14:24 schrieb Richard Stallman:

>     With C-x d I opened a directory with TeX sources etc. I sorted by 
> time
>     and saw a missfont.log file. I opened it with v, read its contents,
>
> At this point, if you switch back to the dired buffer, has its font
> changed already?

Instantly

When Aquamacs has launched it uses its default:

	Fontset: -*-lucida 
grande*-medium-r-normal--14-*-*-*-*-*-fontset-lucida14

When I open the dired buffer, now a new fontset is chosen:

	Fontset: -apple-monaco*-medium-r-normal--12-*-*-*-*-*-fontset-monaco12

And when I now type v or e on the TeX file it opens in

	Fontset: -apple-monaco*-medium-r-normal--12-*-*-*-*-*-fontset-monaco12

Then it happened, when I returned to the dired buffer, that it used the 
default lucida14 fontset.


Aquamacs has some other peculiarities too. For example I saved the 
fontset descriptions into files. Since the buffers contained non-ASCII 
characters, a *Warning* buffer opened in its own new frame -- but in 
the minibuffer of the other frame, that one containing the fontset 
description, I was prompted to select a coding system. Same happens 
when you try to let Aquamacs complete for example the file name into 
which to save the fontset description. A new frame opens or is re-used 
completely for the *Completions* buffer, while the minibuffer in the 
other frame ... I think you know already! Using Aquamacs you get easily 
confused ...

>
> Can you provide us with a complete self-contained test case?
>

I think you actually don't need to care that much about error 
descriptions on Aquamacs, that are very specific to it. David Reitter 
mentioned that we users should use the 'Send Bug Report...' menu item. 
I tried it for the first time and he corrected the issue and correct 
the Aquamacs distribution too.

If he would make the *Warning* and *Help* and *Completions* buffers 
appear in the same frame, not taking away the prompt from the 
minibuffer ...

--
Greetings

   Pete

If you're not confused, you're not paying attention