From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: M-: (org-display-outline-path) doesn't work correctly Date: Fri, 14 Mar 2014 13:28:13 +0100 Message-ID: <87r465otgi.fsf@gmail.com> References: <8738inscnt.fsf@gmail.com> <87zjkvxxnb.fsf@bzg.ath.cx> <87siqnquyh.fsf@gmail.com> <87d2hrwg3m.fsf@bzg.ath.cx> <87eh27qrxd.fsf@gmail.com> <87mwgvia6t.fsf@bzg.ath.cx> <87a9cvqo2k.fsf@gmail.com> <87fvmmih18.fsf@yahoo.fr> <878usepbur.fsf@gmail.com> <87zjkuguzq.fsf@yahoo.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52904) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WORFa-00014D-R1 for emacs-orgmode@gnu.org; Fri, 14 Mar 2014 08:30:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WORFV-0000Qw-5a for emacs-orgmode@gnu.org; Fri, 14 Mar 2014 08:30:10 -0400 Received: from plane.gmane.org ([80.91.229.3]:58608) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WORFU-0000Py-Vq for emacs-orgmode@gnu.org; Fri, 14 Mar 2014 08:30:05 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WORFU-0002ab-9H for emacs-orgmode@gnu.org; Fri, 14 Mar 2014 13:30:04 +0100 Received: from g231107118.adsl.alicedsl.de ([92.231.107.118]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Mar 2014 13:30:04 +0100 Received: from tjolitz by g231107118.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Mar 2014 13:30:04 +0100 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 Nicolas Richard writes: > Thorsten Jolitz writes: >> only that promptly another message is shown (I can't use sit-for in >> the program): > > sit-for was just to demonstrate the problem introduced solely by M-:. > That problem is not present when using interactive commands (i.e. those > a user can actually use), and no sit-for should be necessary in all > pratical situations. > >> ,----------------------------- >> | Wrote /home/my/tmpdir/myfile >> `----------------------------- > > Obviously you should find out what's writing to that file after your > (message ...) statement. I'm not an outshine/outorg user, I have no idea > what does it. found it: ,--------------------------------------------------------------------- | Command: write-region start end filename &optional append visit | | This function writes the region (of the current buffer) delimited by | start and end into the file specified by filename. | | [...] | | Normally, write-region displays a message `Wrote file filename' in | the echo area. If visit is neither t nor nil nor a string, then this | message is inhibited. This feature is useful for programs that use | files for internal purposes, files which the user does not need to | know about. `--------------------------------------------------------------------- so ,------------------------------------------- | (write-region nil nil filename nil 'VISIT) `------------------------------------------- gets rid of the message. -- cheers, Thorsten