bug#5266: Per-host settings

bug#5266: Per-host settings

[Reuben Thomas]

Hi,

I want to set my default face to a different size depending on the
host I'm on. Alternatively, I'd like to set it to a particular pixel
size regardless of the DPI setting (because that's what I'm really
trying to do!).

I can see a couple of ways of doing this:

1. Use X resources.

2. Use /bin/hostname.

In case 1, how do I set the size desired for an Xft font?

In case 2, how do I cope with the following comment I find in my
current customization file:

  ;; custom-set-faces was added by Custom.
  ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.

?

I used to set an X resource Xft.dpi to the same value on all hosts,
but that doesn't seem to affect Emacs 23.

-- 
http://rrt.sc3d.org
Matthew 5:37: tri-state logic considered harmful

bug#5266: Per-host settings

[Andreas Schwab]

Reuben Thomas <rrt@sc3d.org> writes:

> In case 1, how do I set the size desired for an Xft font?

You can use family:pixelsize=px as font name.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

bug#5266: Per-host settings

[Reuben Thomas]

2009/12/25 Andreas Schwab <schwab@linux-m68k.org>:
> Reuben Thomas <rrt@sc3d.org> writes:
>
>> In case 1, how do I set the size desired for an Xft font?
>
> You can use family:pixelsize=px as font name.

Thanks. How do I make an X resource setting take precedence over a
customization? Currently, I have:

emacs.font: xft:Deja Vu Sans Mono:pixelsize=14

but even after erasing the customization for "default" face, this
seems to have no effect.

It would be easier if I could set a pixel size customization, but as
far as I can see there's no way to do that?

-- 
http://rrt.sc3d.org
Belief marks the line at which our thinking stops (Carse)

bug#5266: Per-host settings

[Reuben Thomas]

2010/1/5 Jan Djärv <jan.h.d@swipnet.se>:
> That is not the right syntax, And the family name is probably wrong also (no
> space in DejaVu).  On my machine:

Thanks; bizarrely, the family name, which as you say was wrong, was
copied from a working setting for urxvt; I guess it must somehow make
allowances for spaces; what you suggested:

> emacs.font: DejaVu Sans Mono:pixelsize=14

seems to work fine.

> But you should really use just Monospace and have fonts.config map it for
> you to DejaVu (which it probably does).

I don't have a fonts.config file. To what does it belong? My Ubuntu
system seems to use fontconfig, and "monospace" seems to be used as
DejaVu Sans Mono's default family, though whether that means the
default monospace font is DejaVu Sans Mono, I don't know; certainly
under GNOME I have configured DejaVu Sans Mono as the default
monospaced font in its font preferences.

>> It would be easier if I could set a pixel size customization, but as
>> far as I can see there's no way to do that?
>
> You have to fiddle the height parameter to get what you want.

But of course that doesn't work, as height is dpi-dependent, which is
where I came in: trying to get a dpi-independent, i.e. pixel-based
setting (happens to work better for me across different machines, as I
can't easily seem to get per-machine settings any other way, given
that my Emacs configuration files are synchronised between my
machines, so that my environment is kept up to date on all of them).

-- 
http://rrt.sc3d.org
Matthew 5:37: tri-state logic considered harmful

bug#5266: Per-host settings

[Jan Djärv]

Reuben Thomas skrev:
> 2010/1/5 Jan Djärv <jan.h.d@swipnet.se>:
>> That is not the right syntax, And the family name is probably wrong also (no
>> space in DejaVu).  On my machine:
> 
> Thanks; bizarrely, the family name, which as you say was wrong, was
> copied from a working setting for urxvt; I guess it must somehow make
> allowances for spaces; what you suggested:
> 
>> emacs.font: DejaVu Sans Mono:pixelsize=14
> 
> seems to work fine.
> 

There actually is a Gnome format and a fontconfig format for font names.  When 
you say :pixelsize=14, Emacs assumes fontconfig.  Maybe Deja Vu is ok in the 
Gnome format.

>> But you should really use just Monospace and have fonts.config map it for
>> you to DejaVu (which it probably does).
> 
> I don't have a fonts.config file. To what does it belong? My Ubuntu
> system seems to use fontconfig, and "monospace" seems to be used as
> DejaVu Sans Mono's default family, though whether that means the
> default monospace font is DejaVu Sans Mono, I don't know; certainly
> under GNOME I have configured DejaVu Sans Mono as the default
> monospaced font in its font preferences.

/etc/fonts/fonts.conf and also files in /etc/fonts/conf.d.  On my system,
/etc/fonts/conf.d/60-latin.conf maps monospace to DejaVu Sans Mono.


	Jan D.

bug#5266: Per-host settings

[James Cloos]

>>>>> "Jan" == Jan Djärv <jan.h.d@swipnet.se> writes:

Jan> There actually is a Gnome format and a fontconfig format for font
Jan> names.  When you say :pixelsize=14, Emacs assumes fontconfig.  Maybe
Jan> Deja Vu is ok in the Gnome format.

Fontconfig's algorithm for matching fonts should ignore (most?) spaces.

I just tested:

  :; fc-match 'Deja Vu Serif-14.4'
  DejaVuSerif.ttf: "DejaVu Serif" "Book"

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

bug#5266: Per-host settings

[Reuben Thomas]

2010/1/9 Jan Djärv <jan.h.d@swipnet.se>:
> Reuben Thomas skrev:
>>
>> I don't have a fonts.config file. To what does it belong? My Ubuntu
>> system seems to use fontconfig, and "monospace" seems to be used as
>> DejaVu Sans Mono's default family, though whether that means the
>> default monospace font is DejaVu Sans Mono, I don't know; certainly
>> under GNOME I have configured DejaVu Sans Mono as the default
>> monospaced font in its font preferences.
>
> /etc/fonts/fonts.conf and also files in /etc/fonts/conf.d.  On my system,
> /etc/fonts/conf.d/60-latin.conf maps monospace to DejaVu Sans Mono.

Got it, I have that too. Thanks. I think I prefer to ask specifically
for DejaVu Sans Mono, though I guess that if that's true I should just
copy the current 60-latin.conf into ~/.fonts.conf ?

-- 
http://rrt.sc3d.org
tempus sicut sagittus autem fructus sicut banana

bug#5266: Per-host settings

[Jan Djärv]

Sure, but Emacs has its own parser.

    Jan D.

10 jan 2010 kl. 18.35 skrev James Cloos <cloos@jhcloos.com>:

>>>>>> "Jan" == Jan Djärv <jan.h.d@swipnet.se> writes:
>
> Jan> There actually is a Gnome format and a fontconfig format for font
> Jan> names.  When you say :pixelsize=14, Emacs assumes fontconfig.   
> Maybe
> Jan> Deja Vu is ok in the Gnome format.
>
> Fontconfig's algorithm for matching fonts should ignore (most?)  
> spaces.
>
> I just tested:
>
>  :; fc-match 'Deja Vu Serif-14.4'
>  DejaVuSerif.ttf: "DejaVu Serif" "Book"
>
> -JimC
> -- 
> James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

bug#5266: Per-host settings

[Jan Djärv]

10 jan 2010 kl. 18.47 skrev Reuben Thomas <rrt@sc3d.org>:

> 2010/1/9 Jan Djärv <jan.h.d@swipnet.se>:
>>
>> /etc/fonts/fonts.conf and also files in /etc/fonts/conf.d.  On my  
>> system,
>> /etc/fonts/conf.d/60-latin.conf maps monospace to DejaVu Sans Mono.
>
> Got it, I have that too. Thanks. I think I prefer to ask specifically
> for DejaVu Sans Mono, though I guess that if that's true I should just
> copy the current 60-latin.conf into ~/.fonts.conf ?
>

No need, files in /etc are used. You only need  ~/.fonts.conf if  
additions or changes to them are needed.

     Jan D.

bug#5266: Per-host settings

[Reuben Thomas]

2010/1/10 Jan Djärv <jan.h.d@swipnet.se>:
>
>
> 10 jan 2010 kl. 18.47 skrev Reuben Thomas <rrt@sc3d.org>:
>
>> 2010/1/9 Jan Djärv <jan.h.d@swipnet.se>:
>>>
>>> /etc/fonts/fonts.conf and also files in /etc/fonts/conf.d.  On my system,
>>> /etc/fonts/conf.d/60-latin.conf maps monospace to DejaVu Sans Mono.
>>
>> Got it, I have that too. Thanks. I think I prefer to ask specifically
>> for DejaVu Sans Mono, though I guess that if that's true I should just
>> copy the current 60-latin.conf into ~/.fonts.conf ?
>>
>
> No need, files in /etc are used. You only need  ~/.fonts.conf if additions
> or changes to them are needed.

My point was rather that I wanted to protect against the default
monotype font changing in the system files. Since I'd rather do this
once and for all rather than once per system, the logical thing to do
seemed to be to copy the current system setting (which maps monospace
to DejaVu Mono Sans) to my home directory's settings (which are
synched between all the machines I use).

-- 
http://rrt.sc3d.org
Matthew 5:37: tri-state logic considered harmful

bug#5266: Per-host settings

[Jan Djärv]

Reuben Thomas skrev 2010-01-10 22.02:
> 2010/1/10 Jan Djärv<jan.h.d@swipnet.se>:
>>
>>
>> 10 jan 2010 kl. 18.47 skrev Reuben Thomas<rrt@sc3d.org>:
>>
>>> 2010/1/9 Jan Djärv<jan.h.d@swipnet.se>:
>>>>
>>>> /etc/fonts/fonts.conf and also files in /etc/fonts/conf.d.  On my system,
>>>> /etc/fonts/conf.d/60-latin.conf maps monospace to DejaVu Sans Mono.
>>>
>>> Got it, I have that too. Thanks. I think I prefer to ask specifically
>>> for DejaVu Sans Mono, though I guess that if that's true I should just
>>> copy the current 60-latin.conf into ~/.fonts.conf ?
>>>
>>
>> No need, files in /etc are used. You only need  ~/.fonts.conf if additions
>> or changes to them are needed.
>
> My point was rather that I wanted to protect against the default
> monotype font changing in the system files. Since I'd rather do this
> once and for all rather than once per system, the logical thing to do
> seemed to be to copy the current system setting (which maps monospace
> to DejaVu Mono Sans) to my home directory's settings (which are
> synched between all the machines I use).
>

Ah, ok.  That makes sense.

	Jan D.

bug#5266: Per-host settings

[Glenn Morris]

Is there still an Emacs issue here, and if so could someone summarize
what it is?

bug#5266: Per-host settings

[Chong Yidong]

Glenn Morris <rgm@gnu.org> writes:

> Is there still an Emacs issue here, and if so could someone summarize
> what it is?

No, AFAICT.  Closing the bug.