unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mathias Dahl <brakjoller@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: image-dired shows images as text
Date: Fri, 21 Dec 2007 16:27:27 +0100	[thread overview]
Message-ID: <uabo4131c.fsf@gmail.com> (raw)
In-Reply-To: mailman.5287.1198227357.18990.help-gnu-emacs@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> Instead of:
>> 
>>   (call-process shell-file-name nil nil nil shell-command-switch command)
>> 
>> why not separate the command and switches and use:
>> 
>>   (call-process command nil nil nil command-switches)
>
> These two methods are not exactly equivalent: in the first, `command'
> can be something understood and interpreted by a shell, including
> pipes, redirections, etc.  In the seconds, it must be a name of an
> executable program file.
>
> But I have no idea whether this difference is of any importance for
> the case in point.

Good points. And, again, patches are welcome.

If I get the time I might do something about this over the
holidays. It's largely a matter of how much it itches however...

/Mathias

  parent reply	other threads:[~2007-12-21 15:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5189.1198025951.18990.help-gnu-emacs@gnu.org>
2007-12-19 17:05 ` image-dired shows images as text Mathias Dahl
2007-12-19 20:47   ` winuser
2007-12-19 23:03     ` Nick Roberts
     [not found]     ` <mailman.5251.1198106666.18990.help-gnu-emacs@gnu.org>
2007-12-20 15:47       ` Mathias Dahl
2007-12-20 21:41         ` winuser
     [not found]         ` <mailman.5279.1198186888.18990.help-gnu-emacs@gnu.org>
2007-12-20 22:01           ` Mathias Dahl
2007-12-21  3:43             ` winuser
     [not found]             ` <mailman.5286.1198208612.18990.help-gnu-emacs@gnu.org>
2007-12-21  4:24               ` nullius.filius
2007-12-21  1:40         ` Nick Roberts
2007-12-21  8:55           ` Eli Zaretskii
     [not found]           ` <mailman.5287.1198227357.18990.help-gnu-emacs@gnu.org>
2007-12-21 15:27             ` Mathias Dahl [this message]
2007-12-21 21:13               ` Nick Roberts
     [not found]               ` <mailman.5313.1198272679.18990.help-gnu-emacs@gnu.org>
2008-01-02 13:32                 ` Mathias Dahl
2007-12-27 23:16   ` Allan
2007-12-28  0:45     ` Nick Roberts
     [not found]     ` <mailman.5445.1198802776.18990.help-gnu-emacs@gnu.org>
2007-12-28  6:28       ` Allan
2007-12-28  7:59         ` nullius.filius
2007-12-29  3:31           ` Allan
2007-12-28  8:15         ` Nick Roberts
     [not found]         ` <mailman.5449.1198829754.18990.help-gnu-emacs@gnu.org>
2007-12-29  3:43           ` Allan
2007-12-29 23:35             ` Nick Roberts
     [not found]             ` <mailman.5507.1198973294.18990.help-gnu-emacs@gnu.org>
2007-12-30  2:46               ` Allan
2007-12-30  4:53                 ` Nick Roberts
     [not found]                 ` <mailman.5508.1198990422.18990.help-gnu-emacs@gnu.org>
     [not found]                   ` <uir2dok4e.fsf@earthlink.net>
2008-01-01 20:49                     ` Nick Roberts
2007-12-19  0:59 winuser
2007-12-19  2:06 ` Nick Roberts
2007-12-19 15:11   ` winuser
2007-12-19 15:38     ` Peter Dyballa
2007-12-19 21:15     ` Nick Roberts

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=uabo4131c.fsf@gmail.com \
    --to=brakjoller@gmail.com \
    --cc=help-gnu-emacs@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.
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).