From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Subject: Re: [New exporter] Should there be an option to kill/exit the dispatcher without using it Date: Sat, 16 Feb 2013 21:45:25 -0500 Message-ID: <51204445.5010506@verizon.net> References: <511F8D94.6030600@verizon.net> <511F91BB.2050102@verizon.net> <874nhc5p12.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U6uG0-00038S-6y for emacs-orgmode@gnu.org; Sat, 16 Feb 2013 21:45:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U6uFy-0002Ff-Uk for emacs-orgmode@gnu.org; Sat, 16 Feb 2013 21:45:36 -0500 Received: from vms173013pub.verizon.net ([206.46.173.13]:52874) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U6uFy-0002FV-Nh for emacs-orgmode@gnu.org; Sat, 16 Feb 2013 21:45:34 -0500 Received: from [192.168.1.2] ([unknown] [70.215.0.160]) by vms173013.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0MIC00LGFFNMEC00@vms173013.mailsrvcs.net> for emacs-orgmode@gnu.org; Sat, 16 Feb 2013 20:45:23 -0600 (CST) In-reply-to: <874nhc5p12.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hello, Nicolas, On 2/16/2013 9:09 AM, Nicolas Goaziou wrote: > Hello, > > Charles writes: > >> I'm not sure if my immediate follow up was sent to the list. >> >> I forgot about C-g. >> >> Charlie Millar >> >> On 2/16/2013 8:45 AM, Charles wrote: >>> System Windows 7, 64 bit >>> Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN >>> Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) >>> >>> It appears that there is no simple option in the export dispatcher to >>> either switch to and then kill or simply kill the export dispatcher UI >>> (or buffer) if you do not want to use it after you call it. >>> >>> I called up the new dispatcher only for a look-see and no more. >>> >>> After C-c C-e, the point remained in the original buffer. I then wanted >>> to kill/exit the dispatcher without using it. >>> >>> 1. I attempted to switch to the dispatcher. >>> >>> a. C-x exported the original buffer to XOXO. (no chance to enter >>> the "b" key) >>> >>> b. M-x produced "Wrong type argument: character, 134217848." There >>> was no chance to enter "switch buffer" after M-x. >>> >>> 2. Just for fun I entered "q" and it produced "No command associated >>> with key q." >>> >>> In all three cases the dispatcher remained open but not visible. I was >>> then able to switch to the dispatcher and kill it. > > If you see XOXO export, you're not looking at the new exporter > interface. > > > Regards, > You are right. I was not looking at the new exporter. For that matter, I did not understand how to invoke the new exporter in a Windows 7 set up. That said, when I do load the new exporter as described in the release notes 7.9.2 on my system, the "q" key does not show on the dispatcher ui; however, pressing q does exit the dispatcher. On my Cygwin setup (same machine) the export dispatcher does show q as quit or exit. I update the org files in Cygwin using git, usually once per day. I looked at org/lisp and find that the exporter is now ox-[name]. Is that correct? Perhaps when the ox-[name] files become available in the org/lisp in Org 8 this option will appear in a plain Windows set up (if there is such a thing). I therefore conclude that someone has already suggested adding the line "q for quit", that it has been implemented in the bleeding edge and I over looked any messages to that effect and my research was poorly executed. Best, Charlie