We discussed how to show characters missing in a font a while ago. Here is an example of how Firefox handles it. It shows four hex digits in a square.
The Emacs User manual says this in "(emacs) Optional Mode Line":
Emacs can optionally display the time and system load in all mode
lines. To enable this feature, type `M-x display-time' or customize
the option `display-time-mode'. The information added to the mode line
usually appears after the buffer name, before the mode names and their
parentheses. It looks like this:
HH:MMpm L.LL
Here HH and MM are the hour and minute, followed always by `am' or
`pm'. L.LL is the average number of running processes in the whole
system recently.
The last sentence is inaccurate, at least on GNU/Linux: there, the
load average shows the number of processes that are either running or
ready to run (i.e. waiting in the scheduler's ready-to-run queues). I
believe the same is true for any Unix system that supports this
feature.
If the reader goes by the manual, she will be unable to explain values
for load average that are larger than the number of processors in the
system.
Do we want to make this description more accurate, perhaps at the
price of making it more technical? An alternative would be not to
tell the units in which L.LL is measured, making it more vague. In
that case, perhaps saying something like "values larger than the
number of processors indicate processing congestion" would be enough.
(Continue reading)
At the moment, ELP reports the following functions as the most expensive
while scrolling through a large .lisp file (almost 10k lines):
jit-lock-function 703 4.114131 0.0058522489
jit-lock-fontify-now 703 4.107315 0.0058425533
font-lock-fontify-region 705 4.0757660000 0.0057812283
font-lock-default-fontify-region 705 4.0608700000 0.0057600992
font-lock-fontify-keywords-region 705 1.8490479999 0.0026227631
Byte-compiling these files results in the following timings:
jit-lock-function 703 3.4189879999 0.0048634253
jit-lock-fontify-now 703 3.4116139999 0.0048529359
font-lock-fontify-region 703 3.3229810000 0.0047268577
font-lock-default-fontify-region 703 3.3077700000 0.0047052204
font-lock-fontify-keywords-region 703 1.6209109999 0.0023057055
(CVS version from late April.)
Difference is over half a second, so perhaps it'd make sense to
ship these functions byte-compiled?
-T.
PS. This is the first scrolling through the file. Later scrolling is
much snappier due to jit-lock.
It looks like the Emacs bugtracker is in trouble: ------- Start of forwarded message ------- Your message has been enqueued and undeliverable for 1 hour to the following recipients: Recipient address: 3443-done <at> emacsbugs.donarmstrong.com Reason: unable to deliver this message after 1 hour Delivery attempt history for your mail: Fri, 03 Jul 2009 19:47:53 +0300 (IDT) Temporary error returned by SMTP partner. smtp;452 4.4.5 Insufficient disk space; try again later Fri, 03 Jul 2009 19:15:47 +0300 (IDT) Temporary error returned by SMTP partner. smtp;452 4.4.5 Insufficient disk space; try again later Fri, 03 Jul 2009 18:50:33 +0300 (IDT) Temporary error returned by SMTP partner. smtp;452 4.4.5 Insufficient disk space; try again later Fri, 03 Jul 2009 18:45:26 +0300 (IDT) Temporary error returned by SMTP partner. smtp;452 4.4.5 Insufficient disk space; try again later The mail system will continue to try to deliver your message for an additional 1 hour.(Continue reading)
Next Wednesday, July 8, I will make the 23.0.96 pretest from the EMACS_23_1_RC branch. Unless unexpected serious issues come to light, this will be the final pretest; the 23.1 release will be made two weeks afterwards, on July 29.
Dan, I have a comment about this change committed today:
2009-07-03 Dan Nicolaescu <dann <at> ics.uci.edu>
* callproc.c (child_setup): Use #else instead of a separate #ifdef.
This change is perfectly okay syntactically and semantically, of
course. What bothers me is that it made two unrelated code snippets
look as if they do similar or related things on two different
platforms, because now they are in two sibling branches of the same
#ifdef.
However, this is a matter of style and personal preferences, so I'll
let Stefan and Yidong decide.
The new function w32_set_user_model_id installed by this change:
2009-06-30 Jason Rumney <jasonr <at> gnu.org>
* emacsclient.c (w32_give_focus): Use GetModuleHandle for library
that is already loaded.
(w32_set_user_model_id): New function.
(main): Use it to associate emacsclient with emacs (bug#1849).
causes GCC to print a warning while compiling emacsclient:
emacsclient.c: In function `w32_set_user_model_id':
emacsclient.c:399: warning: parameter names (without types) in function declaration
I don't want to mess with this myself because I don't have access to
Windows 7 to make sure I don't break the change.
Is there an easy way to get custom's widget appearance and tab binding etc without also getting the custom menus? This is useful when using the widget libraries outside of custom.
Try going to www.dn.se with firefox and copy a word with swedish characters into an emacs buffer: inför should rather be: inför (I'm not sure if the error will be properly visible in the email.) Is Firefox doing the wrong thing, or Emacs? Is it a setup problem on my part? My expectation is that the characters should be copied in unicode to the clipboard, and then properly into an emacs buffer. Gedit does the right thing. -- -- Joakim Verona
Hello,
Is there any way to specify different fonts for the same character
with different preferred charsets?
For example, I want to display cyrillic/greek characters using
jisx0208.1983 fonts (wide characters) in Japanese charset texts, and
iso8859-* fonts (narrow characters) in other context (such as email
from other countries).
In other word, how can I specify different fonts for the following two
characters?
-----------
character: д (1076, #o2064, #x434)
preferred charset: cyrillic-iso8859-5
(Right-Hand Part of ISO/IEC 8859/5 (Latin/Cyrillic): ISO-IR-144)
code point: 0x54
syntax: w which means: word
category:
.:Base, Y:2-byte Cyrillic, c:Chinese, h:Korean, j:Japanese, y:Cyrillic
buffer code: #xD0 #xB4
file code: ESC #x2C #x4C #x54 (encoded by coding system iso-2022-7bit)
display: by this font (glyph code)
x:-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso8859-5 (#xD4)
Character code properties: customize what to show
name: CYRILLIC SMALL LETTER DE
general-category: Ll (Letter, Lowercase)
(Continue reading)Hi, Pursuant to this [1] thread on the carbon Emacs mailing list, I'm writing in with a small request regarding the documentation for fontsets in Emacs 23. I know that fonts, fontsets and charsets are one of the more complicated aspects of Emacs, but I think for this exact reason the documentation for fontsets and charsets should be beefed up. Everything in the current docs is correct, but it is such a complicated issue that I think a more basic, ramped-up (almost tutorial-style) approach would be very helpful, particularly for readers unfamiliar with the issue to begin with. In detail: 1. Clearer separation of Linux, Windows and Mac font issues – they seem to be very different. 2. A glossary. What is a charset, what is a font registry, what is a script name symbol, what is encoding and how are these things related? A ground-up explanation of the ecology of bytes, encodings, charsets and fonts would be great. Even, dare I say it, a diagram. This stuff is very confusing. 3. What are the relevant functions and variables? As a non-expert user of middling programming ability, I was totally baffled by set-(Continue reading)fontset- font and all the possible permutations of its arguments. Likewise for create-fontset-from-fontset-spec. Since those two functions seem to be the weapons of choice for font manipulation, their descriptions could stand to be about four times as long as they are, with LOTS more examples. And when you're trying to get your fontsets right (particularly with multiple languages), you need to see lists of possible charsets and registries. These lists are in variables like
RSS Feed107967 |
|---|
