From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel@gnu.org, luangruo@yahoo.com, rms@gnu.org
Subject: Re: svg library ideas
Date: Fri, 03 Feb 2023 10:00:24 +0200 [thread overview]
Message-ID: <83sffnuqjr.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk-ggb4BvVxhwY1cTgBHahr9JTwYFkUiB-sjq0XF-eBf2A@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Fri, 3 Feb 2023 07:39:04 +0100)
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Fri, 3 Feb 2023 07:39:04 +0100
>
> > Building anything with Rust also involves downloading a lot of binary
> code off the internet, and I am not quite comfortable with that.
>
> And, on top, it's extremely painful in platforms were librsvg is not available. Would it make sense to look at
> using the ICEWM library in Emacs as an alternative? Downloading and compiling it as part of the process of
> building Emacs seems less painful than building librsvg...
AFAIU, IceWM is an X11 window manager, so how could it be an
alternative for librsvg, which is a library for displaying SVG images?
next prev parent reply other threads:[~2023-02-03 8:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 6:39 Re: svg library ideas Pedro Andres Aranda Gutierrez
2023-02-03 8:00 ` Eli Zaretskii [this message]
2023-02-03 11:25 ` Jean Louis
2023-02-03 12:31 ` Po Lu
2023-02-03 13:37 ` Jean Louis
2023-02-03 12:42 ` Eli Zaretskii
2023-02-03 13:56 ` Yuri Khan
2023-02-04 7:06 ` Jean Louis
2023-02-04 8:49 ` Eli Zaretskii
2023-02-04 18:38 ` Jean Louis
2023-02-05 4:29 ` Richard Stallman
2023-02-04 7:07 ` Jean Louis
[not found] <87lelo15vw.fsf.ref@yahoo.com>
2023-01-27 13:09 ` Po Lu
2023-01-27 16:36 ` Jean Louis
2023-01-29 5:18 ` Richard Stallman
2023-01-29 5:29 ` Po Lu
2023-01-29 6:44 ` Jim Porter
2023-01-29 6:51 ` Eli Zaretskii
2023-01-31 4:19 ` Richard Stallman
2023-01-31 5:16 ` Po Lu
2023-02-02 5:03 ` Richard Stallman
2023-02-02 5:18 ` Po Lu
2023-02-03 0:19 ` Gregory Heytings
2023-01-29 6:43 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sffnuqjr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=paaguti@gmail.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).