unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: some dired hints should be background jobs
Date: Mon, 03 Mar 2003 06:13:02 +0200	[thread overview]
Message-ID: <2593-Mon03Mar2003061302+0200-eliz@elta.co.il> (raw)
In-Reply-To: <877kbh9v5q.fsf@alice.dynodns.net> (message from John Wiegley on Sun, 02 Mar 2003 17:00:01 -0700)

> From: John Wiegley <johnw@gnu.org>
> Date: Sun, 02 Mar 2003 17:00:01 -0700
> 
> > I know so little about MS Windows (I use GNU/Linux) that I do not
> > really understand the above.  Do you mean we could not make "xpdf *
> > &" the default because MS Windows does not understand & and hence
> > it would not be portable?  Does MS Windows have a notion of job
> > control?  It must have a notion of asynchronous command since it is
> > a windowing system.
> 
> Yep, that's exactly what I mean.  On some Windows shells you can use
> "start", but not all.

Which ones don't support `start'?  AFAIK, all of them do.

> In fact, I don't believe there is any common
> way of backgrounding a job that gets run via shell invocation.

Actually, I think this is the default on Windows: a GUI program
always opens its own window, and the shell that invoked it doesn't
wit for it.  If not, you could use `start'.

> This could mean that "&" is just a UNIX(ish) thing.

That's true in the sense that the "&" syntax is not understood by
stock Windows shells.

      parent reply	other threads:[~2003-03-03  4:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01  3:41 some dired hints should be background jobs Luc Teirlinck
2003-03-02 22:10 ` John Wiegley
2003-03-02 23:30   ` Luc Teirlinck
2003-03-03  0:00     ` John Wiegley
2003-03-03  0:33       ` Luc Teirlinck
2003-03-03  1:16         ` Luc Teirlinck
2003-03-03  4:13       ` Eli Zaretskii [this message]

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=2593-Mon03Mar2003061302+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=emacs-devel@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).