David Caldwell | 1 Apr 01:17 2009

bug#2835: 23.0.92; Info is missing help for some mac specific variables.

I was poking around and noticed that the mac-* have been renamed to ns-* 
names. They are still not documented, however. Sorry to cause any confusion 
by refering to their old names.
Jason Rumney | 1 Apr 02:07 2009
Picon

bug#2830: 23.0.91; Private use area

jonathan <at> doves.demon.co.uk wrote:

>    I used the mouse. Shift-click didn't behave as it used to, but I found "Set Default Font..." on the
"Options" menu on the menu bar. It seemed to work as I expected: the font is distinctive enough that I'm sure
the buffer was using the font I chose (Code2000). But the private-use characters were displayed as empty boxes.
>   

Because these characters are from the Private Use Area, Emacs cannot 
assume that just because a font has glyphs at those code points that 
they are the right glyphs. You will need to explicitly tell Emacs that 
you want to use Code2000 to represent the PUA range:

(set-fontset-font t '(#xe000 . #xf8ff) (font-spec :family "Code2000"))

Jason Rumney | 1 Apr 01:55 2009
Picon

bug#2835: 23.0.92; Info is missing help for some mac specific variables.

David Caldwell wrote:
> The following variables exist but are not documented in the emacs info:
>
> mac-allow-anti-aliasing

Other font backends that support anti-aliasing use an :antialias 
property on the font to disable or use a different type of antialiasing 
for that font. There are a lot of extra font properties like this that 
aren't documented either, especially in the xft and w32 font backends.

trentbuck | 1 Apr 02:11 2009
Picon

bug#2837: 23.0.91; tramp: ssh passphrase vs. password

Just now I tried to open /ssh:dhcp98:/ and it asked me for "dhcp98's
password".  It *should* have asked me for the passphrase for one of my
SSH keys (id_rsa).  This either means that the prompt is misleading
(i.e. it wants my passphrase) or worse, that it genuinely wants to use
password-based authentication (i.e. ignoring my key).

In GNU Emacs 23.0.91.1 (i486-pc-linux-gnu)
 of 2009-03-30 on elegiac, modified by Debian
 (emacs-snapshot package, version 1:20090329-1)
configured using `configure  '--build' 'i486-linux-gnu' '--host' 'i486-linux-gnu' '--prefix=/usr'
'--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var'
'--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes'
'--enable-locallisppath=/etc/emacs-snapshot:/etc/emacs:/usr/local/share/emacs/23.0.91/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.0.91/site-lisp:/usr/share/emacs/site-lisp'
'--with-x=no' '--without-dbus' '--without-sound' 'build_alias=i486-linux-gnu'
'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -DSITELOAD_PURESIZE_EXTRA=5000 -g -O2'
'LDFLAGS=-g -Wl,--as-needed' 'CPPFLAGS=''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: C
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_AU.utf8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

(Continue reading)

Stefan Monnier | 1 Apr 03:11 2009
Picon

bug#2830: 23.0.91; Private use area

> Because these characters are from the Private Use Area, Emacs cannot assume
> that just because a font has glyphs at those code points that they are the
> right glyphs. You will need to explicitly tell Emacs that you want to use
> Code2000 to represent the PUA range:

> (set-fontset-font t '(#xe000 . #xf8ff) (font-spec :family "Code2000"))

It would probably make sense to just "use the default font" for any PUA
chars supported by that font.  It's not strictly correct, but in the
absence of any additional info, it seems like a good heuristic.

        Stefan

Stefan Monnier | 1 Apr 03:14 2009
Picon

bug#2833: 23.0.92; Bug in Directory Variables

>   1. Create a dir and write the following to file .dir-locals in the dir
>      created:

> ((latex-mode . ((fill-column . 78)
>                 (coding . "latin-1"))))

>   2. Open or create a .tex file in that dir
>   3. C-h v fill-column RET to check the value 
>   4. Change 78 to another value say 75

How do you change it?  with C-x f ?

>   5. Re-open the .tex file and you will see fill-column has a value 78
>      NOT 75

How do you "re-open" it?

        Stefan

YAMAMOTO Mitsuharu | 1 Apr 03:22 2009
Picon

bug#2835: 23.0.92; Info is missing help for some mac specific variables.

>>>>> On Wed, 01 Apr 2009 07:55:52 +0800, Jason Rumney <jasonr <at> gnu.org> said:

>> The following variables exist but are not documented in the emacs
>> info:
>> 
>> mac-allow-anti-aliasing

Confusingly, this is not a variable that controls anti-aliasing, but
it changes a font rendering engine so it uses lighter anti-aliasing.
This facility seems to be deprecated as of Mac OS X 10.5, so I'd
suggest removing this variable together with the corresponding NS
variable, ns-use-qd-smoothing.

> Other font backends that support anti-aliasing use an :antialias
> property on the font to disable or use a different type of
> antialiasing for that font. There are a lot of extra font properties
> like this that aren't documented either, especially in the xft and
> w32 font backends.

Still this applies to another NS variable, ns-antialias-text.

				     YAMAMOTO Mitsuharu
				mituharu <at> math.s.chiba-u.ac.jp

Emacs bug Tracking System | 1 Apr 03:25 2009

Processed: Re: bug#2836: 23.0.92; The bottom of my font (Monaco 10) is cut off on Mac OS X

Processing commands for control <at> emacsbugs.donarmstrong.com:

> reassign 2836 emacs,ns
bug#2836: 23.0.92; The bottom of my font (Monaco 10) is cut off on Mac OS X
Warning: Unknown package 'ns'
bug reassigned from package `emacs' to `emacs,ns'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Don Armstrong
(administrator, Emacs bugs database)

Kenichi Handa | 1 Apr 03:44 2009

bug#2830: 23.0.91; Private use area

In article <jwvd4bxuqlk.fsf-monnier+emacsbugreports <at> gnu.org>, Stefan Monnier
<monnier <at> iro.umontreal.ca> writes:

> > Because these characters are from the Private Use Area, Emacs cannot assume
> > that just because a font has glyphs at those code points that they are the
> > right glyphs. You will need to explicitly tell Emacs that you want to use
> > Code2000 to represent the PUA range:

> > (set-fontset-font t '(#xe000 . #xf8ff) (font-spec :family "Code2000"))

> It would probably make sense to just "use the default font" for any PUA
> chars supported by that font.  It's not strictly correct, but in the
> absence of any additional info, it seems like a good heuristic.

I agree.  I'll modify the setting of the default fontset to
do that.

---
Kenichi Handa
handa <at> m17n.org

YAMAMOTO Mitsuharu | 1 Apr 04:02 2009
Picon

bug#2835: 23.0.92; Info is missing help for some mac specific variables.

>>>>> On Wed, 01 Apr 2009 10:22:37 +0900, YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp> said:

>>> The following variables exist but are not documented in the emacs
>>> info:
>>> 
>>> mac-allow-anti-aliasing

> Confusingly, this is not a variable that controls anti-aliasing, but
> it changes a font rendering engine so it uses lighter anti-aliasing.

Sorry, this description itself seems to be confusing.  I meant, "if
the variable is set to non-nil, it selects another font rendering
engine whose rendering results in lighter anti-aliasing."

				     YAMAMOTO Mitsuharu
				mituharu <at> math.s.chiba-u.ac.jp


Gmane