font size

font size

[Arash Bijanzadeh]

Hello ecerybody!
I wanna know if it is possible to change the font size in the X client 
of emacs? and how? please help me!

-- 
 ,           , 
 /             \ 
((__-^^-,-^^-__)) 
 `-_---' `---_-' 
  `--|o` 'o|--' 
     \  `  / 
      ): :( 
      :o_o: 
       "-" 
A.bejan

Re: font size

[G Anna]

> Date: Tue, 23 Apr 2002 20:54:23 +0430
> From: Arash Bijanzadeh <a.bijanzadeh@linuxiran.org>
> Subj: font size
> 
> Hello ecerybody!
> I wanna know if it is possible to change the font size in the X client 
> of emacs? and how? please help me!

In your ~/.emacs add the following lines.  Remember to choose an
appropriate font.

(setq default-frame-alist
      '((width . 80)
	(height . 40)
	(font . "-misc-fixed-medium-r-normal--15-120-100-100-c-90-iso8859-1")
	(background-color . "black")
	(foreground-color . "light blue")
	(menu-bar-lines . 1)))

Also try shift+left-mouse-button to get the font menu.

HTH

anna

font size

[Massimo Alonzo]

Hi all,

how can I increase fonts size for my Latex/Fortran documents?


Thank you
Massimo

font size

[Baloff]

Hello
I am trying to change the font size.
after reading in info info on how to seach the info. I was able to
find in info emacs ps-font-size should do it.

but when I type ps<tab> in the mini buffer I get

Possible completions are:
ps-despool			   ps-line-lengths
ps-mode				   ps-nb-pages-buffer
ps-nb-pages-region		   ps-print-buffer
ps-print-buffer-with-faces	   ps-print-customize
ps-print-region			   ps-print-region-with-faces
ps-spool-buffer			   ps-spool-buffer-with-faces
ps-spool-region			   ps-spool-region-with-faces

nothing about font size. 

help please

thanks

Re: font size

[Peter Dyballa]

Am 29.07.2005 um 06:24 schrieb Baloff:

> I am trying to change the font size.
>

Try S-down-mouse-1 or M-x mouse-set-font!

--
Greetings

   Pete

Without vi there is only GNU Emacs



--
Mit friedvollen Grüßen

   Pete

Mit Jazz statt Bomben gegen die Taliban!

Re: font size

[Eli Zaretskii]

> From: Baloff <washdc@wash.edu>
> Date: 29 Jul 2005 14:24:37 +1000
> 
> I am trying to change the font size.
> after reading in info info on how to seach the info. I was able to
> find in info emacs ps-font-size should do it.
> 
> but when I type ps<tab> in the mini buffer I get
> 
> Possible completions are:
> ps-despool			   ps-line-lengths
> ps-mode				   ps-nb-pages-buffer
> ps-nb-pages-region		   ps-print-buffer
> ps-print-buffer-with-faces	   ps-print-customize
> ps-print-region			   ps-print-region-with-faces
> ps-spool-buffer			   ps-spool-buffer-with-faces
> ps-spool-region			   ps-spool-region-with-faces
> 
> nothing about font size. 

Try loading ps-print first, like this:

    M-x load-library RET ps-print RET

and then try typing "ps TAB" again.

(Some variables are only defined when the respective package is loaded
into Emacs.)

Btw, ps-font-size is only for the ps-print feature, it will not affect
the fonts used for display.  Are you sure this is what you need?

Re: font size

[Baloff]

Eli Zaretskii <eliz@gnu.org> writes:

> > From: Baloff <washdc@wash.edu>
> > Date: 29 Jul 2005 14:24:37 +1000
> > 
> > I am trying to change the font size.
> > after reading in info info on how to seach the info. I was able to
> > find in info emacs ps-font-size should do it.
> > 
> > but when I type ps<tab> in the mini buffer I get
> > 
> > Possible completions are:
> > ps-despool			   ps-line-lengths
> > ps-mode				   ps-nb-pages-buffer
> > ps-nb-pages-region		   ps-print-buffer
> > ps-print-buffer-with-faces	   ps-print-customize
> > ps-print-region			   ps-print-region-with-faces
> > ps-spool-buffer			   ps-spool-buffer-with-faces
> > ps-spool-region			   ps-spool-region-with-faces
> > 
> > nothing about font size. 
> 
> Try loading ps-print first, like this:
> 
>     M-x load-library RET ps-print RET
> 
> and then try typing "ps TAB" again.
> 
> (Some variables are only defined when the respective package is loaded
> into Emacs.)
> 
> Btw, ps-font-size is only for the ps-print feature, it will not affect
> the fonts used for display.  Are you sure this is what you need?

I am trying to increase the font size displayed on the screen. plus I
don't know what S-down-mouse-1 or M-x mouse-set-font! mean.
what is S-down-mouse-1 any way?

Re: font size

[Peter Dyballa]

Am 30.07.2005 um 12:15 schrieb Baloff:

> what is S-down-mouse-1 any way?
>

You press the shift key and while holding it down you press usually the 
left-most mouse button. Then you can let go both keys.

Or you type C-h t.

--
Greetings

   Pete

Bake Pizza not war!

Re: font size

[Eli Zaretskii]

> From: Baloff <washdc@wash.edu>
> Date: 30 Jul 2005 20:15:38 +1000
> 
> I am trying to increase the font size displayed on the screen.

Then the ps-* stuff is not what you want.

> plus I don't know what S-down-mouse-1 or M-x mouse-set-font! mean.
> what is S-down-mouse-1 any way?

S-down-mouse-1 means hold the Shift key and click the left mouse
button.

Sounds like you need to read the tutorial and the few basic chapters
of the manual.  The node "Mouse Commands" is one that I recommend.

Re: font size

[Tim X]

Baloff <washdc@wash.edu> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > > From: Baloff <washdc@wash.edu>
> > > Date: 29 Jul 2005 14:24:37 +1000
> > > 
> > > I am trying to change the font size.
> > > after reading in info info on how to seach the info. I was able to
> > > find in info emacs ps-font-size should do it.
> > > 
> > > but when I type ps<tab> in the mini buffer I get
> > > 
> > > Possible completions are:
> > > ps-despool			   ps-line-lengths
> > > ps-mode				   ps-nb-pages-buffer
> > > ps-nb-pages-region		   ps-print-buffer
> > > ps-print-buffer-with-faces	   ps-print-customize
> > > ps-print-region			   ps-print-region-with-faces
> > > ps-spool-buffer			   ps-spool-buffer-with-faces
> > > ps-spool-region			   ps-spool-region-with-faces
> > > 
> > > nothing about font size. 
> > 
> > Try loading ps-print first, like this:
> > 
> >     M-x load-library RET ps-print RET
> > 
> > and then try typing "ps TAB" again.
> > 
> > (Some variables are only defined when the respective package is loaded
> > into Emacs.)
> > 
> > Btw, ps-font-size is only for the ps-print feature, it will not affect
> > the fonts used for display.  Are you sure this is what you need?
> 
> I am trying to increase the font size displayed on the screen. plus I
> don't know what S-down-mouse-1 or M-x mouse-set-font! mean.
> what is S-down-mouse-1 any way?
> 

Firstly, I'd recommend reading the tutorial C-h t (Control and h
together then t). Also check out the info pages on emacs. 

In emacs, font related stuff is covered by the term 'face'. Try M-x
customize-face <ret> (where M-x means hit Meta plus x and Meta is
*usually* the Alt key)

If your running on Linux under X, you can also use X resource settings
(see info pages). You can also set the font on the command line with
-font. 

Tim

-- 
Tim Cross
The e-mail address on this message is FALSE (obviously!). My real e-mail is
to a company in Australia called rapttech and my login is tcross - if you 
really need to send mail, you should be able to work it out!

Merging the pgtk branch

[Eli Zaretskii]

We would like to merge the pgtk branch onto master soon, so that it
could be included in Emacs 28.1.  Below please find some preliminary
comments from reviewing the branch's code.

I would ask people here who are interested in this feature to please
build the branch, both --with-pgtk and without it, and report any
problems they see (using "M-x report-emacs-bug", preferably).

Here are my preliminary comments from looking at the branch.  Full
disclosure: I know almost nothing about GTK, so please forgive me any
silly questions/remarks I may have due to this ignorance.

> -install: all install-arch-indep install-etcdoc install-arch-dep install-$(NTDIR) blessmail install-eln
> +install: all install-arch-indep install-etcdoc install-arch-dep install-$(NTDIR) blessmail install-eln install-gsettings-schemas
>  	@true

Does this mean gsettings-schemas will be installed by non-PGTK builds
as well?  If not, where are the conditions to prevent that?

> +    if test $HAVE_IMAGEMAGICK != yes; then
> +      IMAGEMAGICK_MODULE="MagickWand-6.Q16HDRI >= 6.3.5 MagickWand-6.Q16HDRI != 6.8.2 MagickWand-6.Q16HDRI < 7 MagickCore-6.Q16HDRI >= 6.9.9 MagickCore-6.Q16HDRI < 7"
> +      EMACS_CHECK_MODULES([IMAGEMAGICK], [$IMAGEMAGICK_MODULE])
> +    fi

What is this change about?  is it related to PGTK?

> +HAVE_CAIRO=no
> +if test "${HAVE_X11}" = "yes" -o "$window_system" = pgtk; then
> +  if test "${with_cairo}" != "no"; then
> +    CAIRO_REQUIRED=1.12.0
> +    CAIRO_MODULE="cairo >= $CAIRO_REQUIRED"
> +    EMACS_CHECK_MODULES(CAIRO, $CAIRO_MODULE)
> +    if test $HAVE_CAIRO = yes; then
> +      AC_DEFINE(USE_CAIRO, 1, [Define to 1 if using cairo.])
> +    else
> +      AC_MSG_ERROR([cairo requested but not found.])
> +    fi
> +
> +    CFLAGS="$CFLAGS $CAIRO_CFLAGS"
> +    LIBS="$LIBS $CAIRO_LIBS"
> +    AC_SUBST(CAIRO_CFLAGS)
> +    AC_SUBST(CAIRO_LIBS)
> +  fi
> +fi

Does the PGTK build require Cairo?  The above seems to imply it does.
If it does, I think the --with-pgtk description should say so.

> +if test "${window_system}" = "pgtk"; then
> +   FONT_OBJ="ftfont.o ftcrfont.o"
> +fi

Does this mean the PGTK build doesn't support HarfBuzz?  Or am I
misreading the meaning of the above change?

> diff --git a/lib-src/emacsclient.c b/lib-src/emacsclient.c
> index 8346524..8fa571f 100644
> --- a/lib-src/emacsclient.c
> +++ b/lib-src/emacsclient.c
> @@ -603,7 +603,12 @@ decode_options (int argc, char **argv)
>        alt_display = "w32";
>  #endif
 
> +#ifdef HAVE_PGTK
> +      display = egetenv ("WAYLAND_DISPLAY");
> +      alt_display = egetenv ("DISPLAY");
> +#else
>        display = egetenv ("DISPLAY");
> +#endif

The WAYLAND_DISPLAY variable should be documented in the Emacs manual,
where all the environment variables Emacs uses are documented.

> @@ -165,9 +168,9 @@ gui--selection-value-internal
>  Call `gui-get-selection' with an appropriate DATA-TYPE argument
>  decided by `x-select-request-type'.  The return value is already
>  decoded.  If `gui-get-selection' signals an error, return nil."
> -  (let ((request-type (if (eq window-system 'x)
> +  (let ((request-type (if (memq window-system '(x pgtk))
>                            (or x-select-request-type
> -                              '(UTF8_STRING COMPOUND_TEXT STRING))
> +                              '(UTF8_STRING COMPOUND_TEXT STRING text/plain\;charset=utf-8))
>                          'STRING))

Is it useful to have "text/plain\;charset=utf-8" here when
window-system is 'x', not 'pgtk'?

> --- a/lisp/server.el
> +++ b/lisp/server.el
> @@ -900,12 +900,17 @@ server-create-window-system-frame
>        )
 
>      (cond (w
> -           (server--create-frame
> -            nowait proc
> -            `((display . ,display)
> -              ,@(if parent-id
> -                    `((parent-id . ,(string-to-number parent-id))))
> -              ,@parameters)))
> +           (condition-case nil
> +               (server--create-frame
> +                nowait proc
> +                `((display . ,display)
> +                  ,@(if parent-id
> +                        `((parent-id . ,(string-to-number parent-id))))
> +                  ,@parameters))
> +             (error
> +              (server-log "Window system unsupported" proc)
> +              (server-send-string proc "-window-system-unsupported \n")
> +              nil)))

Why is this change needed?

> +(defcustom pgtk-pop-up-frames 'fresh
> +  "Non-nil means open files upon request from the Workspace in a new frame.
> +If t, always do so.  Any other non-nil value means open a new frame
> +unless the current buffer is a scratch buffer."
> +  :type '(choice (const :tag "Never" nil)
> +                 (const :tag "Always" t)
> +                 (other :tag "Except for scratch buffer" fresh))

Is this really PGTK-specific?

> +  :version "23.1"

That version tag is definitely incorrect, should be 28.1.

> +;; Set to use font panel instead
> +(declare-function pgtk-popup-font-panel "pgtkfns.c" (&optional frame))
> +(defalias 'x-select-font 'pgtk-popup-font-panel "Pop up the font panel.
> +This function has been overloaded in Nextstep.")
> +(defalias 'mouse-set-font 'pgtk-popup-font-panel "Pop up the font panel.
> +This function has been overloaded in Nextstep.")

Is Nextstep relevant to the PGTK build?

> +;; Default fontset.  This is mainly here to show how a fontset
> +;; can be set up manually.  Ordinarily, fontsets are auto-created whenever
> +;; a font is chosen by
> +(defvar pgtk-standard-fontset-spec
> +  ;; Only some code supports this so far, so use uglier XLFD version
> +  ;; "-pgtk-*-*-*-*-*-10-*-*-*-*-*-fontset-standard,latin:Courier,han:Kai"
> +  (mapconcat 'identity
> +             '("-*-Monospace-*-*-*-*-10-*-*-*-*-*-fontset-standard"
> +               "latin:-*-Courier-*-*-*-*-10-*-*-*-*-*-iso10646-1"
> +               "han:-*-Kai-*-*-*-*-10-*-*-*-*-*-iso10646-1"
> +               "cyrillic:-*-Trebuchet$MS-*-*-*-*-10-*-*-*-*-*-iso10646-1")
> +             ",")
> +  "String of fontset spec of the standard fontset.
> +This defines a fontset consisting of the Courier and other fonts.
> +See the documentation of `create-fontset-from-fontset-spec' for the format.")

This seems to be copied from ns-win.el?  Are the font names relevant
to PGTK?

> +;; Functions for color panel + drag
> +(defun pgtk-face-at-pos (pos)
> +  (let* ((frame (car pos))
> +         (frame-pos (cons (cadr pos) (cddr pos)))
> +         (window (window-at (car frame-pos) (cdr frame-pos) frame))
> +         (window-pos (coordinates-in-window-p frame-pos window))
> +         (buffer (window-buffer window))
> +         (edges (window-edges window)))
> +    (cond
> +     ((not window-pos)
> +      nil)
> +     ((eq window-pos 'mode-line)
> +      'mode-line)
> +     ((eq window-pos 'vertical-line)
> +      'default)
> +     ((consp window-pos)
> +      (with-current-buffer buffer
> +        (let ((p (car (compute-motion (window-start window)
> +                                      (cons (nth 0 edges) (nth 1 edges))
> +                                      (window-end window)
> +                                      frame-pos
> +                                      (- (window-width window) 1)
> +                                      nil
> +                                      window))))
> +          (cond
> +           ((eq p (window-point window))
> +            'cursor)
> +           ((and mark-active (< (region-beginning) p) (< p (region-end)))
> +            'region)
> +           (t
> +	    (let ((faces (get-char-property p 'face window)))
> +	      (if (consp faces) (car faces) faces)))))))
> +     (t
> +      nil))))

Is this function needed?  It uses compute-motion, which cannot be a
good idea, so I wonder what is this needed for.

> +  ;; Don't let Emacs suspend under PGTK.
> +  (add-hook 'suspend-hook 'pgtk-suspend-error)

What's this about?  If PGTK doesn't want to be suspended, why do this
via a hook?

> +(defun pgtk-preedit-text (e)
> +  (interactive "e")

Please add a meaningful doc string for this command.

> --- a/src/.gdbinit
> +++ b/src/.gdbinit
> @@ -41,6 +41,9 @@ handle SIGUSR2 noprint pass
>  # debugging.
>  handle SIGALRM ignore
 
> +# On selection send failed.
> +handle SIGPIPE nostop noprint

This cannot be unconditional, please condition it on PGTK.

> -#ifdef USE_GTK
> +#if defined(USE_GTK)

I don't understand this and many similar changes that replaced
"#ifdef" with "#if defined" and "#ifndef" with "#if !defined", without
adding more conditions.  Is this a left-over from some debugging?  If
so, please don't make such redundant changes.

> +#ifdef HAVE_PGTK
> +  mark_pgtkterm();
> +#endif

Our style conventions are to leave one space between the function's
name and the left parenthesis, like this:

  mark_pgtkterm ();

Please follow this style here and elsewhere in the PGTK code.

> --- a/src/atimer.c
> +++ b/src/atimer.c
> @@ -309,11 +309,13 @@ set_alarm (void)
>  	  ispec.it_value = atimers->expiration;
>  	  ispec.it_interval.tv_sec = ispec.it_interval.tv_nsec = 0;
>  # ifdef HAVE_TIMERFD
> -	  if (timerfd_settime (timerfd, TFD_TIMER_ABSTIME, &ispec, 0) == 0)
> -	    {
> -	      add_timer_wait_descriptor (timerfd);
> -	      return;
> -	    }
> +	  if (timerfd >= 0) {
> +	    if (timerfd_settime (timerfd, TFD_TIMER_ABSTIME, &ispec, 0) == 0)
> +              {
> +                add_timer_wait_descriptor (timerfd);
> +                return;
> +              }
> +	  }

Why was this change needed?

Also, please use our style conventions for braces: they should be on
the next line, as in the original code above.

>  # ifdef HAVE_TIMERFD
> -      timerfd_settime (timerfd, TFD_TIMER_ABSTIME, &ispec, 0);
> +      if (timerfd >= 0)
> +	timerfd_settime (timerfd, TFD_TIMER_ABSTIME, &ispec, 0);
>  # endif

Same question here: why was this change needed?

> +# elif defined HAVE_PGTK
> +  /* pgtk emacs does not want timerfd. */
> +  return true;

And this.

> -#ifdef USE_GTK
> +#if defined(USE_GTK)
> +#ifndef HAVE_PGTK

This could be done in a single conditional:

  #if defined USE_GTK && !defined HAVE_PGTK

> +#define EMACS_TYPE_FIXED        (emacs_fixed_get_type ())
> +#define EMACS_IS_FIXED(obj)     (G_TYPE_CHECK_INSTANCE_TYPE ((obj), EMACS_TYPE_FIXED))

Why is this unconditional?

> +extern GType emacs_fixed_get_type (void);

And this.

> --- a/src/font.c
> +++ b/src/font.c
> @@ -5584,7 +5584,11 @@ syms_of_font (void)
>    syms_of_xftfont ();
>  #endif  /* HAVE_XFT */
>  #endif  /* not USE_CAIRO */
> -#endif	/* HAVE_X_WINDOWS */
> +#else	/* not HAVE_X_WINDOWS */
> +#ifdef USE_CAIRO
> +  syms_of_ftcrfont ();
> +#endif
> +#endif	/* not HAVE_X_WINDOWS */

Why was this needed? how did the Cairo build do this initialization
until now?

> -#if defined (HAVE_XFT) || defined (HAVE_FREETYPE) || defined (HAVE_NS)
> +#if defined (HAVE_XFT) || defined (HAVE_FREETYPE) || defined (HAVE_NS) || defined(HAVE_PGTK)
>  extern Lisp_Object font_build_object (int, Lisp_Object, Lisp_Object, double);
>  #endif

Doesn't the PGTK build define HAVE_XFT and HAVE_FREETYPE?

> - `pc' for a direct-write MS-DOS frame.
> + `pc' for a direct-write MS-DOS frame,
> + `pgtk' for an Emacs frame running entirely in GTK.

Since you call this "pure GTK", let's say so here as well.

> @@ -4775,10 +4779,17 @@ gui_set_border_width (struct frame *f, Lisp_Object arg, Lisp_Object oldval)
>    if (border_width == f->border_width)
>      return;
 
> +#ifndef HAVE_PGTK
>    if (FRAME_NATIVE_WINDOW (f) != 0)
>      error ("Cannot change the border width of a frame");
> +#endif
 
>    f->border_width = border_width;
> +
> +#ifdef HAVE_PGTK
> +  if (FRAME_TERMINAL (f)->frame_rehighlight_hook)
> +    (*FRAME_TERMINAL (f)->frame_rehighlight_hook) (f);
> +#endif

Why is the above done only for PGTK?

> @@ -6367,7 +6386,12 @@ focus (where a frame immediately loses focus when it's left by the mouse
>  to set the size of a frame in pixels, to maximize frames or to make them
>  fullscreen.  To resize your initial frame pixelwise, set this option to
>  a non-nil value in your init file.  */);
> +#ifndef HAVE_PGTK
>    frame_resize_pixelwise = 0;
> +#else
> +  /* https://gitlab.gnome.org/GNOME/mutter/-/issues/396 */
> +  frame_resize_pixelwise = true;
> +#endif

Why the PGTK-specific setting here?

> @@ -132,7 +136,9 @@ ftcrfont_open (struct frame *f, Lisp_Object entity, int pixel_size)
>    filename = XCAR (val);
>    size = XFIXNUM (AREF (entity, FONT_SIZE_INDEX));
>    if (size == 0)
> +  {
>      size = pixel_size;
> +  }

These braces are redundant here.

> +#ifndef PGTK_TRACE
> +#define PGTK_TRACE(fmt, ...) ((void) 0)
> +#endif

Do we still need PGTK_TRACE (and all its calls)?

> +#ifndef HAVE_PGTK
>    if (FRAME_X_DISPLAY (f) != DEFAULT_GDK_DISPLAY ())
>      {
>        GdkDisplay *gdpy = gdk_x11_lookup_xdisplay (FRAME_X_DISPLAY (f));
> @@ -137,6 +150,17 @@ xg_set_screen (GtkWidget *w, struct frame *f)
>        else
>          gtk_window_set_screen (GTK_WINDOW (w), gscreen);
>      }
> +#else
> +  if (FRAME_X_DISPLAY(f) != DEFAULT_GDK_DISPLAY ())

So FRAME_X_P returns zero for PGTK, but FRAME_X_DISPLAY is still
relevant for it?  Isn't that confusing?

> -  f->output_data.x->hint_flags = 0;
> +  f->output_data.xp->hint_flags = 0;

Why did you need this change (and others like it)?  The "x" part here
has an important mnemonic value.

> +#ifdef PGTK_DEBUG

Do we need this PGTK_DEBUG stuff and its callers?

> +static struct redisplay_interface pgtk_redisplay_interface = {
> +  pgtk_frame_parm_handlers,
> +  gui_produce_glyphs,
> +  gui_write_glyphs,
> +  gui_insert_glyphs,
> +  gui_clear_end_of_line,
> +  pgtk_scroll_run,
> +  pgtk_after_update_window_line,
> +  NULL, // gui_update_window_begin,
> +  NULL, // gui_update_window_end,

Please use C-style comments, not C++-style comments (here and
elsewhere).

> +#define XFillRectangle(d, win, gc, x, y, w, h) \
> +    ( cairo_rectangle (cr, x, y, w, h), cairo_fill (cr) )

I wonder why you need this XFillRectangle macro in code that is pure
PGTK?

> +static int draw_glyphs_debug(const char *file, int lineno,
> +			     struct window *w, int x, struct glyph_row *row,
> +			     enum glyph_row_area area, ptrdiff_t start, ptrdiff_t end,
> +			     enum draw_glyphs_face hl, int overlaps)
> +{
> +  return draw_glyphs(w, x, row, area, start, end, hl, overlaps);
> +}
> +#define draw_glyphs(w, x, r, a, s, e, h, o) \
> +  draw_glyphs_debug(__FILE__, __LINE__, w, x, r, a, s, e, h, o)
> +

The above looks like some left-over from debugging?  Do we still need
it?

> @@ -32748,7 +32763,7 @@ mouse_face_from_buffer_pos (Lisp_Object window,
>    hlinfo->mouse_face_face_id
>      = face_at_buffer_position (w, mouse_charpos, &ignore,
>  			       mouse_charpos + 1,
> -                               !hlinfo->mouse_face_hidden, -1, 0);
> +			       !hlinfo->mouse_face_hidden, -1, 0);

This looks like whitespace change?

Thanks again for working on this important feature.

Font size (was: Merging the pgtk branch)

[Kévin Le Gouguec]

Hello,

AFAICT the branch builds and runs fine --with-pgtk --with-xwidgets
--with-cairo on Debian 10 (XFCE).

One hiccup: unless I'm mistaken, this build does not consult
~/.Xresources anymore.  That led me to discover --with-gconf and
font-use-system-font (I did not use these options previously); I am now
a bit confused about how font sizes work.

On master, with font-use-system-font set to nil, here is what C-u C-x =
says for various values of emacs.font in ~/.Xresources:

.Xresources¹    C-u C-x =²
9               12
10              13
10.5            14
11              15

¹ "XX" in "emacs.font: DejaVu Sans Mono-XX"
² "XX" in "ftcrhb:-PfEd-DejaVu Sans Mono-normal-normal-normal-*-XX-*-*-*-m-0-iso10646-1"

On master --with-gconf and feature/pgtk, with font-use-system-font set
to t, here is what C-u C-x = says for various GSettings:

GSettings³      C-u C-x =
9               12
10              13
10.5            ERROR (see below)
11              15

³ "XX" in "gsettings org.gnome.desktop.interface monospace-font-name 'DejaVu Sans Mono XX'"

As it happens, "10.5" (reported as "14" inside Emacs) is the size I find
the most comfortable on my screen; unfortunately if I run:

$ gsettings set org.gnome.desktop.interface monospace-font-name 'DejaVu Sans Mono 10.5'

Emacs emits a warning:

> set-face-attribute: Font not available: #<font-spec nil nil DejaVu\
> Sans\ Mono\ 10\.5 nil nil nil nil nil nil nil nil nil ((:name
> . "DejaVu Sans Mono 10.5") (:user-spec . "DejaVu Sans Mono 10.5"))>

Is this expected?  Otherwise, should I report an issue?  (AFAICT it is
not specific to the pgtk branch)

Re: Font size (was: Merging the pgtk branch)

[Eli Zaretskii]

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Yuuki Harano <masm+emacs@masm11.me>, Eli Zaretskii <eliz@gnu.org>
> Date: Wed, 04 Aug 2021 14:53:04 +0200
> 
> One hiccup: unless I'm mistaken, this build does not consult
> ~/.Xresources anymore.

That's by design, AFAIU.  Yuuki even said that not so long ago.

Re: Font size

[Kévin Le Gouguec]

Eli Zaretskii <eliz@gnu.org> writes:

>> One hiccup: unless I'm mistaken, this build does not consult
>> ~/.Xresources anymore.
>
> That's by design, AFAIU.  Yuuki even said that not so long ago.

Right.  To recap my other questions:

1. Why do Xresources and GSettings sizes differ from what C-u C-x =
   reports?

2. Why doesn't "10.5" work with GSettings, despite it working with
   Xresources?

3. Is there a bug to report there?

Re: Font size

[Yuri Khan]

On Wed, 4 Aug 2021 at 20:59, Kévin Le Gouguec <kevin.legouguec@gmail.com> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> One hiccup: unless I'm mistaken, this build does not consult
> >> ~/.Xresources anymore.
> >
> > That's by design, AFAIU.  Yuuki even said that not so long ago.
>
> Right.  To recap my other questions:
>
> 1. Why do Xresources and GSettings sizes differ from what C-u C-x =
>    reports?

Likely because the former are specified in points (1 pt = 1/72 in) and
the latter in pixels (1 px = 1/96 in by default).

Re: Font size

[Eli Zaretskii]

> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Wed, 4 Aug 2021 22:46:25 +0700
> Cc: Eli Zaretskii <eliz@gnu.org>, masm+emacs@masm11.me, 
> 	Emacs developers <emacs-devel@gnu.org>
> 
> > 1. Why do Xresources and GSettings sizes differ from what C-u C-x =
> >    reports?
> 
> Likely because the former are specified in points (1 pt = 1/72 in) and
> the latter in pixels (1 px = 1/96 in by default).

is this tru also for GSettings font sizes in the X+GTK build of Emacs?
Because then we'd need to document that in the "Fonts" section of the
Emacs manual, where all the different methods of specifying a font are
described.

Re: Font size

[Yuri Khan]

On Wed, 4 Aug 2021 at 23:11, Eli Zaretskii <eliz@gnu.org> wrote:

> > > 1. Why do Xresources and GSettings sizes differ from what C-u C-x =
> > >    reports?
> >
> > Likely because the former are specified in points (1 pt = 1/72 in) and
> > the latter in pixels (1 px = 1/96 in by default).
>
> is this tru also for GSettings font sizes in the X+GTK build of Emacs?
> Because then we'd need to document that in the "Fonts" section of the
> Emacs manual, where all the different methods of specifying a font are
> described.

The org.gnome.desktop.interface GSettings schema does not say
explicitly which units the size is specified in, and whether
fractional values are allowed.

    <key name="font-name" type="s">
      <default>'Cantarell 11'</default>
      <summary>Default font</summary>
      <description>
        Name of the default font used by gtk+.
      </description>
    </key>
    <key name="document-font-name" type="s">
      <default>'Cantarell 11'</default>
      <summary>Document font</summary>
      <description>
        Name of the default font used for reading documents.
      </description>
    </key>
    <key name="monospace-font-name" type="s">
      <default>'Source Code Pro 10'</default>
      <summary>Monospace font</summary>
      <description>
        Name of a monospaced (fixed-width) font for use in locations like
        terminals.
      </description>
    </key>

Re: Font size

[Eli Zaretskii]

> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Thu, 5 Aug 2021 00:09:47 +0700
> Cc: Kévin Le Gouguec <kevin.legouguec@gmail.com>, 
> 	masm+emacs@masm11.me, Emacs developers <emacs-devel@gnu.org>
> 
> On Wed, 4 Aug 2021 at 23:11, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > > > 1. Why do Xresources and GSettings sizes differ from what C-u C-x =
> > > >    reports?
> > >
> > > Likely because the former are specified in points (1 pt = 1/72 in) and
> > > the latter in pixels (1 px = 1/96 in by default).
> >
> > is this tru also for GSettings font sizes in the X+GTK build of Emacs?
> > Because then we'd need to document that in the "Fonts" section of the
> > Emacs manual, where all the different methods of specifying a font are
> > described.
> 
> The org.gnome.desktop.interface GSettings schema does not say
> explicitly which units the size is specified in, and whether
> fractional values are allowed.

My question was whether the same units are likely to be used in the
X+GTK build as they are in the PGTK build.  IOW, that your guess of
the units being 1/96 inch is true or false for both of them.

Re: Font size

[Yuri Khan]

On Thu, 5 Aug 2021 at 01:24, Eli Zaretskii <eliz@gnu.org> wrote:

> My question was whether the same units are likely to be used in the
> X+GTK build as they are in the PGTK build.  IOW, that your guess of
> the units being 1/96 inch is true or false for both of them.

I’m not related to GNOME or GTK+ development, but I would be much
surprised if font sizes were specified in anything other than points
(which are 1/72 in, not 1/96 in); and especially if GTK behaved
differently in that regard between X and Wayland and/or depended on
other factors other than poorly configured screen DPI.

Re: Font size

[Robert Pluim]

>>>>> On Thu, 5 Aug 2021 01:33:16 +0700, Yuri Khan <yuri.v.khan@gmail.com> said:

    Yuri> On Thu, 5 Aug 2021 at 01:24, Eli Zaretskii <eliz@gnu.org> wrote:
    >> My question was whether the same units are likely to be used in the
    >> X+GTK build as they are in the PGTK build.  IOW, that your guess of
    >> the units being 1/96 inch is true or false for both of them.

    Yuri> I’m not related to GNOME or GTK+ development, but I would be much
    Yuri> surprised if font sizes were specified in anything other than points
    Yuri> (which are 1/72 in, not 1/96 in); and especially if GTK behaved
    Yuri> differently in that regard between X and Wayland and/or depended on
    Yuri> other factors other than poorly configured screen DPI.

Fontconfig talks about sizes in points (but allows them to be
fractional, the underlying data type is a double)

Robert
-- 

Re: Font size

[Eli Zaretskii]

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  masm+emacs@masm11.me,  Emacs developers
>  <emacs-devel@gnu.org>,  Kévin Le Gouguec
>  <kevin.legouguec@gmail.com>
> Date: Thu, 05 Aug 2021 16:51:57 +0200
> 
> >>>>> On Thu, 5 Aug 2021 01:33:16 +0700, Yuri Khan <yuri.v.khan@gmail.com> said:
> 
>     Yuri> On Thu, 5 Aug 2021 at 01:24, Eli Zaretskii <eliz@gnu.org> wrote:
>     >> My question was whether the same units are likely to be used in the
>     >> X+GTK build as they are in the PGTK build.  IOW, that your guess of
>     >> the units being 1/96 inch is true or false for both of them.
> 
>     Yuri> I’m not related to GNOME or GTK+ development, but I would be much
>     Yuri> surprised if font sizes were specified in anything other than points
>     Yuri> (which are 1/72 in, not 1/96 in); and especially if GTK behaved
>     Yuri> differently in that regard between X and Wayland and/or depended on
>     Yuri> other factors other than poorly configured screen DPI.
> 
> Fontconfig talks about sizes in points (but allows them to be
> fractional, the underlying data type is a double)

I wasn't talking about the Fontconfig format of specifying a font, I
was talking about the GTK format.  They are different, see the node
"Fonts" in the Emacs manual.

Re: Font size (was: Merging the pgtk branch)

[Eli Zaretskii]

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Date: Wed, 04 Aug 2021 14:53:04 +0200
> Cc: Yuuki Harano <masm+emacs@masm11.me>, Eli Zaretskii <eliz@gnu.org>
> 
> $ gsettings set org.gnome.desktop.interface monospace-font-name 'DejaVu Sans Mono 10.5'
> 
> Emacs emits a warning:
> 
> > set-face-attribute: Font not available: #<font-spec nil nil DejaVu\
> > Sans\ Mono\ 10\.5 nil nil nil nil nil nil nil nil nil ((:name
> > . "DejaVu Sans Mono 10.5") (:user-spec . "DejaVu Sans Mono 10.5"))>
> 
> Is this expected?

I don't know if it's expected, but the error message says that the
"10.5" part is not expected there.  What happens if you use "10"
instead of "10.5"?

Re: Font size

[Kévin Le Gouguec]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
>> Date: Wed, 04 Aug 2021 14:53:04 +0200
>> Cc: Yuuki Harano <masm+emacs@masm11.me>, Eli Zaretskii <eliz@gnu.org>
>> 
>> $ gsettings set org.gnome.desktop.interface monospace-font-name 'DejaVu Sans Mono 10.5'
>> 
>> Emacs emits a warning:
>> 
>> > set-face-attribute: Font not available: #<font-spec nil nil DejaVu\
>> > Sans\ Mono\ 10\.5 nil nil nil nil nil nil nil nil nil ((:name
>> > . "DejaVu Sans Mono 10.5") (:user-spec . "DejaVu Sans Mono 10.5"))>
>> 
>> Is this expected?
>
> I don't know if it's expected, but the error message says that the
> "10.5" part is not expected there.  What happens if you use "10"
> instead of "10.5"?

Cf. the paragraph just above:

> On master --with-gconf and feature/pgtk, with font-use-system-font set
> to t, here is what C-u C-x = says for various GSettings:
> 
> GSettings³      C-u C-x =
> 9               12
> 10              13
> 10.5            ERROR (see below)
> 11              15
> 
> ³ "XX" in "gsettings org.gnome.desktop.interface monospace-font-name 'DejaVu Sans Mono XX'"

What I don't understand:

1. How come GSettings/Xresources and Emacs use different "units"?
   (Apologies if the answer lies somewhere in the manual, which it most
   certainly does)

2. Why does 10.5 work with Xresources and not GSettings?

Font size

[Anand Tamariya]

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

Why does this API keep increasing the font size? With a selection, try the
test command.

Alternatively, what's the best way to query the font-size at point and
re-apply using face property?


font-info
[ OPENED-NAME FULL-NAME SIZE *HEIGHT* BASELINE-OFFSET RELATIVE-COMPOSE
    DEFAULT-ASCENT MAX-WIDTH ASCENT DESCENT SPACE-WIDTH AVERAGE-WIDTH
    FILENAME CAPABILITY ]

(defun test(start end)
  (interactive "r")
  (let* ((size (* 10 (aref (font-info (font-at start)) 3))))
    (put-text-property start end 'face
      (list :inherit 'unspecified :height size))))

[-- Attachment #2: Type: text/html, Size: 776 bytes --]

Re: Font size

[Eli Zaretskii]

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Tue, 20 Aug 2024 10:55:45 +0530
> 
> Why does this API keep increasing the font size? With a selection, try the test command.

Because the factor of 10 is wrong, AFAIU.

> Alternatively, what's the best way to query the font-size at point and re-apply using face property?

I don't understand: if you don't want to change the height, then why
do you have :height in the face spec at all?

In any case, :height could be a relative value of 1.0.

Re: Font size

[Anand Tamariya]

[-- Attachment #1: Type: text/plain, Size: 573 bytes --]

> Why does this API keep increasing the font size? With a selection, try
> the test command.
>
> Because the factor of 10 is wrong, AFAIU.
>
Factor of 1 decreases the font size.

> Alternatively, what's the best way to query the font-size at point and
> re-apply using face property?
>
> I don't understand: if you don't want to change the height, then why
> do you have :height in the face spec at all?
>
> In any case, :height could be a relative value of 1.0.
>
 I'm trying to increase/decrease the font size in the selected region. So I
need a base value to work with.

[-- Attachment #2: Type: text/html, Size: 1016 bytes --]

Re: Font size

[Eli Zaretskii]

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Tue, 20 Aug 2024 18:26:15 +0530
> Cc: emacs-devel@gnu.org
> 
> 
>  > Why does this API keep increasing the font size? With a selection, try the test command.
> 
>  Because the factor of 10 is wrong, AFAIU.
> 
> Factor of 1 decreases the font size. 

Yes, because 1 is also wrong.

>  > Alternatively, what's the best way to query the font-size at point and re-apply using face property?
> 
>  I don't understand: if you don't want to change the height, then why
>  do you have :height in the face spec at all?
> 
>  In any case, :height could be a relative value of 1.0.
> 
>  I'm trying to increase/decrease the font size in the selected region. So I need a base value to work with.

And relative values like 1.2 or 0.8 don't fit the bill in your case?
Using relative sizes frees you from the need to compute absolute size
values.

Re: Font size

[Anand Tamariya]

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

> >  I'm trying to increase/decrease the font size in the selected region.
> So I need a base value to work with.
>
> And relative values like 1.2 or 0.8 don't fit the bill in your case?
> Using relative sizes frees you from the need to compute absolute size
> values.
>
I'm exploring a scenario where the text is inside a fixed shape. So
absolute size is important.

[-- Attachment #2: Type: text/html, Size: 623 bytes --]

Re: Font size

[Eli Zaretskii]

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Tue, 20 Aug 2024 19:07:33 +0530
> Cc: emacs-devel@gnu.org
> 
>  >  I'm trying to increase/decrease the font size in the selected region. So I need a base value to work
>  with.
> 
>  And relative values like 1.2 or 0.8 don't fit the bill in your case?
>  Using relative sizes frees you from the need to compute absolute size
>  values.
> 
> I'm exploring a scenario where the text is inside a fixed shape. So absolute size is important. 

Not sure I understand why float values don't do what you want, but you
could find the right value of the factor empirically.  In my case, I
found that 6 is the right value.