From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: rms@gnu.org
Cc: aquamacs-bugs@lists.sourceforge.net, 5902@debbugs.gnu.org
Subject: bug#5902: [Aquamacs-bugs] Re: (no subject)
Date: Tue, 7 Jun 2005 17:11:38 +0200 [thread overview]
Message-ID: <0f8366f36870fb1a257268725f319add__26888.8699160472$1270746515$gmane$org@Web.DE> (raw)
In-Reply-To: <E1Dfd8F-0006gi-9u@fencepost.gnu.org>
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
prev parent reply other threads:[~2005-06-07 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5738cffcf10432a7b6959bcf9b43a726@Web.DE>
2005-06-06 21:58 ` bug#5878: [Aquamacs-bugs] Re: dired / view buffer / wrong theme (was: no subject) David Reitter
2005-06-07 12:24 ` bug#5891: [Aquamacs-bugs] Re: (no subject) Richard Stallman
[not found] ` <E1Dfd8F-0006gi-9u@fencepost.gnu.org>
2005-06-07 15:11 ` Peter Dyballa [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0f8366f36870fb1a257268725f319add__26888.8699160472$1270746515$gmane$org@Web.DE' \
--to=peter_dyballa@web.de \
--cc=5902@debbugs.gnu.org \
--cc=aquamacs-bugs@lists.sourceforge.net \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.