aboutsummaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorDavid Aspinall2012-04-30 13:17:14 +0000
committerDavid Aspinall2012-04-30 13:17:14 +0000
commit72eeead8935ddf733022b2427c2cf2797126f570 (patch)
tree1b47a3e3c118b6fb1367f9d516db1ea64435a7bd /FAQ
parentef584b51fac4be9703d8772b3c20bbeffc5f9fc8 (diff)
Change default Unicode Tokens font back to DejaVU Sans, more reliable without installing STIX.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ95
1 files changed, 56 insertions, 39 deletions
diff --git a/FAQ b/FAQ
index 734f6c8f..c96e6d48 100644
--- a/FAQ
+++ b/FAQ
@@ -31,6 +31,62 @@ A. We distribute compiled .elcs for one version of Emacs, but other
-----------------------------------------------------------------
+Q. I have just installed Emacs, ProofGeneral and a proof assistant.
+ It works but Tokens (e.g. \<Longrightarrow>) are not being displayed
+ as symbols.
+
+A. You need to enable Unicode Tokens by the menu item:
+
+ Proof-General -> Options -> Unicode Tokens
+
+ To enable it automatically every time you use Proof General,
+ use
+
+ Proof-General -> Options -> Save Options
+
+ after doing this.
+
+ Note that we don't do this by default, because from the system's
+ perspective it is difficult to determine if this will succeed ---
+ or just produce funny characters that confuse new users even more.
+
+ If you are using Isabelle, the wrapper script will load Tokens
+ from any location, and you can enable it by passing the option
+ "-x true".
+
+-----------------------------------------------------------------
+
+
+Q. With Unicode symbols enabled, the symbols look a mess, e.g.
+ compressed and overlap one another.
+
+A. Unfortunately this is a bug in the display engine inside
+ certain versions of Emacs, for example the default version
+ of emacs, Emacs 23.3.1 on Ubuntu 11.10, suffers.
+
+ The solution is to switch to another version (e.g. Emacs 23.2).
+ (See Trac#409: http://proofgeneral.inf.ed.ac.uk/trac/ticket/409)
+
+ You may be able to get better results with different fonts, even
+ without upgrading Emacs.
+
+ Proof General uses Deja Vu Sans Mono by default because
+ this often works out-of-the-box. But STIX is better if you
+ install it. See http://www.stixfonts.org/. On Ubuntu try:
+
+ sudo apt-get install fonts-stix
+
+ To change to STIX, either
+
+ M-x customize face RET unicode-tokens-symbol-font-face RET
+
+ and edit to set the family name to "STIXGeneral", or edit
+ the line beginning "(defface unicode-tokens-symbol-font-face" in
+ lib/unicode-tokens.el.
+
+
+-----------------------------------------------------------------
+
Q. Help, I'm stuck!! Emacs keeps telling me "Cannot switch buffers in a
dedicated window"
@@ -76,45 +132,6 @@ A. Unfortunately the architecture of Proof General is designed so
-----------------------------------------------------------------
-Q. I have just installed Emacs, ProofGeneral and a proof assistant.
- It works but Tokens (e.g. \<Longrightarrow>) are not being displayed
- as symbols.
-
-A. You need to enable Unicode Tokens by the menu item:
-
- Proof-General -> Options -> Unicode Tokens
-
- To enable it automatically every time you use Proof General,
- use
-
- Proof-General -> Options -> Save Options
-
- after doing this.
-
- Note that we don't do this by default, because from the system's
- perspective it is difficult to determine if this will succeed ---
- or just produce funny characters that confuse new users even more.
-
- If you are using Isabelle, the wrapper script will load Tokens
- from any location, and you can enable it by passing the option
- "-x true".
-
-
------------------------------------------------------------------
-
-
-Q. With Unicode symbols enabled, arrows and other symbols appear
- compressed and overlap one another.
-
-A. Unfortunately this is a bug in the display engine inside
- certain versions of Emacs, for example the default version
- of emacs, Emacs 23.3.1 on Ubuntu 11.10, suffers.
-
- The solution is to switch to another version (e.g. Emacs 23.2).
- (See Trac#409).
-
------------------------------------------------------------------
-
Q. I'm afraid I got stuck very early on. I sent the following line: