Fixed, I think. https://github.com/OpenIndiana/oi-userland/pull/17583
On Tue, Jun 18, 2024 at 9:16 AM Udo Grabowski (IMK)
wrote:
>
> On 18/06/2024 15:00, Udo Grabowski (IMK) wrote:
> > This could be a clue:
> > 08887: 1: ld.so.1: emacs-gtk-29.3: fatal: gtk_progress_get_type: can't find
> > symb
On 18/06/2024 15:00, Udo Grabowski (IMK) wrote:
This could be a clue:
08887: 1: ld.so.1: emacs-gtk-29.3: fatal: gtk_progress_get_type: can't find
symbol
gtk_progress_get_type is a symbol from gtk2 (deprecated), not in gtk3.
But as far as I can deduce from the dbx library load list and LD_DEBUG
This could be a clue:
08887: 1: ld.so.1: emacs-gtk-29.3: fatal: gtk_progress_get_type: can't find
symbol
gtk_progress_get_type is a symbol from gtk2 (deprecated), not in gtk3.
But as far as I can deduce from the dbx library load list and LD_DEBUG=libs,
none of that is calling libgtk2*, so that
On 18/06/2024 12:51, Udo Grabowski (IMK) wrote:
emacs -nw -q --batch --eval '(message system-configuration-options)' shows
CC=/usr/gcc/13/bin/gcc CXX=/usr/gcc/13/bin/g++ F77=/usr/gcc/13/bin/gfortran
FC=/usr/gcc/13/bin/gfortran ’CFLAGS=-m64 -O3 -I/usr/include/libjpeg8-turbo
-Wl,-L/usr/lib/libjpe
emacs -nw -q --batch --eval '(message system-configuration-options)' shows
CC=/usr/gcc/13/bin/gcc CXX=/usr/gcc/13/bin/g++ F77=/usr/gcc/13/bin/gfortran
FC=/usr/gcc/13/bin/gfortran ’CFLAGS=-m64 -O3 -I/usr/include/libjpeg8-turbo
-Wl,-L/usr/lib/libjpeg8-turbo/lib/amd64 -Wl,-R/usr/lib/libjpeg8-turb
I opened a bug for this:
https://www.illumos.org/issues/16613
emacs-gtk vers 29.3 crashes on startup
On Mon, Jun 17, 2024 at 4:32 PM Gordon Ross wrote:
>
> Before beginning an exploration of which versions expose the font
> problem and which don't, I decided to start with updating the
> installat
Before beginning an exploration of which versions expose the font
problem and which don't, I decided to start with updating the
installation. Now emacs-gtk doesn't work at all. Suggestions?
Output below:
(emacs-gtk:1193): Gtk-ERROR **: 16:25:16.093: GTK+ 2.x symbols
detected. Using GTK+ 2.x and
Am 11.06.24 um 21:34 schrieb Andreas Wacknitz via oi-dev:
Rereading the thread I realized that you are using the nox variant of
emacs and this is bound to the font being used by the terminal window.
I have checked mine here and I don't seem to have the problems you
experienced.
Have you tried to
I am an emacs user and have configured it to use my preferred font.
This
(use-package font
:no-require
:hook (after-init . setup-fonts)
:preface
(defun font-installed-p (font-name)
"Check if a font with FONT-NAME is available."
(find-font (font-spec :name font-name)))
(defun se
Looking into this again. I definitely have this font selected:
$ fc-match "Deja Vu Sans Mono"
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
$ fc-match "Deja Vu Sans Mono-12"
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
It exists, and is a TrueType font.
If I use that font in a mate-terminal pro
Yes, the "bad" one is not antialiased, possibly a bitmap font,
while the "good" one is definitely antialiased, possibly TrueType or OpenType.
-alan-
On 11/21/23 07:25, Gordon Ross wrote:
Thanks. I've confirmed that emacs is using the system font in both builds.
Here are two screen shot
GTK & Pango use fonts from fontconfig, not from X11, so it's not expected
to match xfontsel (which uses X11 fonts). Among other things, Pango 1.44
dropped support for Type 1 & bitmap fonts, which X11/xfontsel still support,
leaving TrueType & OpenType font support. One easy to spot difference,
f
As far as I can tell, the "system" font for mate terminal and such is:
"DejaVu Sans Mono", or
-misc-dejavu sans mono-medium-o-normal--0-0-0-0-p-0-ascii-0
Based on what I see with xfontsel, it looks like emacs may be using:
-misc-dejavu sans light-extralight-r-normal--0-0-0-0-p-0-ascii-0
I tried p
On Wed, Nov 08, 2023 at 05:44:42PM +0100, Andreas Wacknitz wrote:
> If you are using the gtk variant of emacs
That's the one I'm using.
> then it relies on pango for
> font rendering and layout which in case has dropped support for older
> font types a couple of months ago.
> So your problem mig
On Wed, Nov 08, 2023 at 11:28:33AM -0500, Gordon Ross wrote:
> I saw the same after I upgraded, back in July.
> See subject: Emacs font problem in 28.2
Where are you finding this? I can't seem to find it.
--
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-
Am 08.11.23 um 16:36 schrieb Gary Mills:
I recently did an OI upgrade, on one of my systems, from 20220928 to
20231107 (more than a year). Everthing worked normally afterwards
except for emacs. It has a peculiar font, compared to MATE-terminal.
The font appears to be too thin. I'm using the sa
On Wed, Nov 08, 2023 at 06:07:54PM +0200, Toomas Soome via oi-dev wrote:
> sounds like the original font got substituted. If you start emacs from
> command line, does it tell about fonts being replaced?
No, it completely silent. However, when I use the Options menu to
select the system font, my
I saw the same after I upgraded, back in July.
See subject: Emacs font problem in 28.2
On Wed, Nov 8, 2023 at 11:08 AM Toomas Soome via oi-dev
wrote:
>
>
>
> > On 8. Nov 2023, at 17:36, Gary Mills wrote:
> >
> > I recently did an OI upgrade, on one of my systems, from 20220928 to
> > 20231107 (m
> On 8. Nov 2023, at 17:36, Gary Mills wrote:
>
> I recently did an OI upgrade, on one of my systems, from 20220928 to
> 20231107 (more than a year). Everthing worked normally afterwards
> except for emacs. It has a peculiar font, compared to MATE-terminal.
> The font appears to be too thin.
I recently did an OI upgrade, on one of my systems, from 20220928 to
20231107 (more than a year). Everthing worked normally afterwards
except for emacs. It has a peculiar font, compared to MATE-terminal.
The font appears to be too thin. I'm using the same font size as
before, 10 point. What cou
20 matches
Mail list logo
