unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] emacs/lisp image.el
Date: Sun, 30 Aug 2009 01:14:27 +0200	[thread overview]
Message-ID: <f7ccd24b0908291614y30f2874o72e100ab0d98f9d1@mail.gmail.com> (raw)
In-Reply-To: <87ljl2z3ex.fsf@mail.jurta.org>

On Sun, Aug 30, 2009 at 00:46, Juri Linkov<juri@jurta.org> wrote:

> I left `image-jpeg-p' in image.el for the case it's used by some
> external packages or .emacs files since it contains a non-trivial
> algorithm for detecting JFIF/Exif JPEGs.  Even though its name is
> not too specific, its docstring explains what it does.

IMO, it is inconsistent with what image.el (or indeed Emacs) offers;
we don't have functions to detect the different image formats
supported by TIFF, for example.

`image-jpeg-p' was never a published interface, just a helper
function. As a very crude test, googling for it brings a few hits
(plus "image/jpeg" false hits), most of which seem to be from our code
or bug reports. It's unlikely the function has received wide usage
(yes, private libraries and most .emacs files do not appear in Google;
I said "crude").

If removing it is too severe, at least obsoleting it seems to be in
order. It is unused in the sources, too specific, inconsistently
documented, and internal.

    Juanma




  reply	other threads:[~2009-08-29 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1MhBBw-0007QN-2z@cvs.savannah.gnu.org>
2009-08-29  0:21 ` [Emacs-diffs] emacs/lisp image.el Juanma Barranquero
2009-08-29 22:46   ` Juri Linkov
2009-08-29 23:14     ` Juanma Barranquero [this message]
2009-08-30 20:51       ` Juri Linkov
2009-08-31 15:15   ` Chong Yidong
2009-08-31 23:49     ` Stefan Monnier
2009-09-01  0:05       ` Juanma Barranquero

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=f7ccd24b0908291614y30f2874o72e100ab0d98f9d1@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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).