From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18019 invoked from network); 16 Dec 2008 17:08:05 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 16 Dec 2008 17:08:05 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 31877 invoked from network); 16 Dec 2008 17:08:01 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 16 Dec 2008 17:08:01 -0000 Received: (qmail 25757 invoked by alias); 16 Dec 2008 17:07:57 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 26142 Received: (qmail 25746 invoked from network); 16 Dec 2008 17:07:56 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 16 Dec 2008 17:07:56 -0000 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by bifrost.dotsrc.org (Postfix) with ESMTP id EF465801E288 for ; Tue, 16 Dec 2008 18:07:53 +0100 (CET) Received: by nf-out-0910.google.com with SMTP id g13so557392nfb.11 for ; Tue, 16 Dec 2008 09:07:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=uRiBA/QcmGhcwGOGDJ8gDiLGAz/g7an51e1/cesgiDM=; b=NaVuK6x05xabGX/CCkO4bGHVYpLFTqEp2HIRu6LGisL5UCo5429eodICV2drgTZm0V yAG/L2zQJxOcEHCiwcRmEddKexxPlI+DKI+sSCzSJfLcTclMzacai7AGXX8yOBzfS7fa /XGxVAih17fwKUVcjPv9AIFyElV5eDsbxqYsM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=KEY/tSXTM+GL0eQMQWdAGE8aNBhDWRDaMhgHV+8/AB4FGfWwlEqjpRnPQSOJRINSS1 kJ4bJB3nb8wbI6fKuIgpgPM8F7nYe3ViCzCUI+LXwfz/R+EZTdYqIgbzHmqUHDC3b542 iJbNaLCTDeLmIt4z/v8ZFN06xFvWh6q7EyEYA= Received: by 10.210.37.11 with SMTP id k11mr1562782ebk.114.1229447272384; Tue, 16 Dec 2008 09:07:52 -0800 (PST) Received: by 10.210.82.6 with HTTP; Tue, 16 Dec 2008 09:07:50 -0800 (PST) Message-ID: <237967ef0812160907s6481321dnf796fcdcbb93fb1f@mail.gmail.com> Date: Tue, 16 Dec 2008 18:07:50 +0100 From: "Mikael Magnusson" To: zsh-workers@sunsite.dk Subject: Re: PATCH: edit-command-line with spaces in EDITOR In-Reply-To: <20081216153846.GA10426@scru.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081216153846.GA10426@scru.org> X-Virus-Scanned: ClamAV 0.92.1/8767/Tue Dec 16 14:52:17 2008 on bifrost X-Virus-Status: Clean 2008/12/16 Clint Adams : > Apparently people want to set EDITOR to things like > "connect-emacs editor -t". I'm not convinced this is a good idea. If the binary or path to it contains a space, you just broke it. It's probably better to just tell people to make a short wrapper script. Also, if some apps parse spaces in EDITOR and others don't, then you effectively have to _both_ keep the path+binary space-free and not give any arguments. That seems suboptimal. FWIW git interprets spaces in EDITOR but... AFAIK it has always been the name of a binary and nothing more. -- Mikael Magnusson