unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eric Lilja <mindcooler@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Building with image support
Date: Fri, 26 Oct 2007 10:21:50 +0200	[thread overview]
Message-ID: <86sl3y2sm9.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <ffptv3$jlb$1@ger.gmane.org> (Eric Lilja's message of "Thu\, 25 Oct 2007 13\:16\:57 +0200")

Eric Lilja <mindcooler@gmail.com> writes:

> David Kastrup wrote:
>> Eric Lilja <mindcooler@gmail.com> writes:
>>
>>> My question is this: What am I missing without png support, without
>>> tiff support etc? I only work with text with emacs, 90 percent of
>>> the time programming. My original wish has been fullfilled, which
>>> was nice looking toolbars on windows, but I wanted to know if it
>>> might be a good idea to build emacs with support for the other image
>>> formats as well. But if it doesn't matter to what I do with emacs, I
>>> don't want to complicate my "build environment" unnecessarily.
>>
>> You can use Emacs to browse/view images and directories containing
>> them, and there is something like
>> <URL:http://www.gnu.org/software/auctex/preview-latex.html> if you
>> are using LaTeX for writing texts.
>>
>
> Thanks for the quick reply, David. If I get more serious in my attempt
> to learn latex, I will most definetly look into latex preview mode and
> try to build emacs with the image format support it needs for
> that. But as far as the "UI" is concerned, xpm is sufficient, right?

PNG icons supposedly look quite more refined on GTK+, partly due to
better transparency support.

-- 
David Kastrup

  reply	other threads:[~2007-10-26  8:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 10:46 Building with image support Eric Lilja
2007-10-25 11:12 ` David Kastrup
2007-10-25 11:16   ` Eric Lilja
2007-10-26  8:21     ` David Kastrup [this message]
2007-10-26 10:33       ` Eric Lilja
2007-10-26 10:58         ` Jason Rumney
2007-10-28 15:45           ` Eric Lilja
2007-10-26  9:46 ` Richard Stallman
2007-10-26 10:34   ` Eric Lilja

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=86sl3y2sm9.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mindcooler@gmail.com \
    /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).