From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "find lulu" Newsgroups: gmane.emacs.bugs Subject: bug#890: Problem using `etc/emacs.bash' with EmacsW32 Date: Fri, 5 Sep 2008 11:39:52 -0400 Message-ID: <6bb3db200809050839l4e90bd50q80eefe4938144df5@mail.gmail.com> Reply-To: find lulu , 890@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_33896_1723022.1220629192776" X-Trace: ger.gmane.org 1220674422 11127 80.91.229.12 (6 Sep 2008 04:13:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 6 Sep 2008 04:13:42 +0000 (UTC) To: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Sep 06 06:14:37 2008 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KbpC0-0003HB-QA for geb-bug-gnu-emacs@m.gmane.org; Sat, 06 Sep 2008 06:14:37 +0200 Original-Received: from localhost ([127.0.0.1]:45660 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KbpB0-0006Db-NS for geb-bug-gnu-emacs@m.gmane.org; Sat, 06 Sep 2008 00:13:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KbdqS-00049L-KO for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 12:07:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KbdqQ-00047F-Ea for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 12:07:35 -0400 Original-Received: from [199.232.76.173] (port=41876 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KbdqQ-000470-8J for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 12:07:34 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:58765) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KbdqP-0000eQ-BU for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 12:07:33 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m85G7VoU032297; Fri, 5 Sep 2008 09:07:31 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id m85Fo2Rr025185; Fri, 5 Sep 2008 08:50:03 -0700 X-Loop: don@donarmstrong.com Resent-From: "find lulu" Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Fri, 05 Sep 2008 15:50:02 +0000 Resent-Message-ID: Resent-Sender: don@donarmstrong.com X-Emacs-PR-Message: report 890 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by submit@emacsbugs.donarmstrong.com id=B.122062920721992 (code B ref -1); Fri, 05 Sep 2008 15:50:02 +0000 Original-Received: (at submit) by emacsbugs.donarmstrong.com; 5 Sep 2008 15:40:07 +0000 Original-Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m85FdxOn021744 for ; Fri, 5 Sep 2008 08:40:01 -0700 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KbdPj-0004ZT-2c for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 11:39:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KbdPi-0004Z9-Cu for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 11:39:58 -0400 Original-Received: from [199.232.76.173] (port=50870 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KbdPi-0004Z2-8D for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 11:39:58 -0400 Original-Received: from ag-out-0708.google.com ([72.14.246.250]:50633) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KbdPh-0008Pz-8s for bug-gnu-emacs@gnu.org; Fri, 05 Sep 2008 11:39:58 -0400 Original-Received: by ag-out-0708.google.com with SMTP id 31so1060417agc.10 for ; Fri, 05 Sep 2008 08:39:53 -0700 (PDT) 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:mime-version:content-type; bh=a2VwOLmIw8f4UZDUkntD/73Sxvx7qMmnAHFu1oRPBiA=; b=qQseH8yaSRkQHVkOn1Did4sPdzScU6nbpPjB/KtBRLcsUNR02xyP/Xc9CPmhm5xHzv 1tu+Wszk4dRBxG7w3pAOTMZqIYFU2rWu8r8nSK4GiiTeS+wZ0hHoPyuZpmzi89JMJ9/G BpY549Oz7ViQDpo7nq+pP3kWcmxVj36ZVmzaM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=jDa2L7eQdZ+1rKqi9xqhuJEBJXxjZlr3VJZCnvAMqpREPaAvMhCTRTamE6vOtjcEFn 1bUFmvQpovX/fjvQzMkQDO0FM+m1iMVgvGrOfDKhseP4hgBRBYFO7c8lpHzd6xKVe0aH dXex3m6tsFe5lUOerkCNNIOrDGy0iko9qZBHo= Original-Received: by 10.100.197.7 with SMTP id u7mr12785239anf.27.1220629193065; Fri, 05 Sep 2008 08:39:53 -0700 (PDT) Original-Received: by 10.70.20.7 with HTTP; Fri, 5 Sep 2008 08:39:52 -0700 (PDT) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Resent-Date: Fri, 05 Sep 2008 12:07:35 -0400 X-Mailman-Approved-At: Sat, 06 Sep 2008 00:13:31 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:20221 Archived-At: ------=_Part_33896_1723022.1220629192776 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline >>* I am attempting to use the shell script `emacs.bash' that is provided* > > Could you explain why you don't ust use emacsclient directly (together > with its -a argument)? Your question prompts the question "Why does `etc/emacs.bash' exist at all?" The reason for `emacs.bash' to exist is to provide a single, consistent command for editing a file from the bash shell prompt, namely, 'edit'. It is certainly possible to use alternatives to avoid the problems described, but if `etc/emacs.bash' is to be included in the Emacs distribution then it should work for that distribution. In brief, here are the two problems restated (for EmacsW32): 1. `etc/emacs.bash' does not check for the file `~/.emacs.d/server/server' that is created when `server-start' is invoked from EmacsW32. As a result, `emacsclient' is not invoked by the shell function `edit' that is created when `etc/emacs.bash' is sourced. 2. When `server-start' (in `lisp/server.el') is invoked during the Emacs shutdown process, it does not remove the file `~/.emacs.d/server/server' that it created when it was initially invoked. Consequently, additional calls to the shell function 'edit' do not work properly -- namely, `edit' should invoke `emacs' instead of `emacsclient' when there is no instance of the emacs's server running. These problems should be fixed so that `edit' works for EmacsW32 as it does for Emacs on other platforms. Some possible fixes were suggested in the original problem report. ------=_Part_33896_1723022.1220629192776 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 
>> I am attempting to use the shell script `emacs.bash' that is provided
>
> Could you explain why you don't ust use emacsclient directly (together
> with its -a argument)?


Your question prompts the question "Why does `etc/emacs.bash' exist at all?"

The reason for `emacs.bash' to exist is to provide a single, consistent
command for editing a file from the bash shell prompt, namely, 'edit'.


It is certainly possible to use alternatives to avoid the problems described,
but if `etc/emacs.bash' is to be included in the Emacs distribution then it
should work for that distribution.

In brief, here are the two problems restated (for EmacsW32):


1. `etc/emacs.bash' does not check for the file `~/.emacs.d/server/server'
   that is created when `server-start' is invoked from EmacsW32.  As a result,
   `emacsclient' is not invoked by the shell function `edit' that is created

   when `etc/emacs.bash' is sourced.

2. When `server-start' (in `lisp/server.el') is invoked during the Emacs
   shutdown process, it does not remove the file `~/.emacs.d/server/server'
   that it created when it was initially invoked.  Consequently, additional

   calls to the shell function 'edit' do not work properly -- namely, `edit'
   should invoke `emacs' instead of `emacsclient' when there is no instance
   of the emacs's server running.


These problems should be fixed so that `edit' works for EmacsW32 as it does
for Emacs on other platforms.  Some possible fixes were suggested in the
original problem report.

------=_Part_33896_1723022.1220629192776--