emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Sperber <sperber@deinprogramm.de>
To: emacs-orgmode@gnu.org
Cc: Robert Pluim <rpluim@gmail.com>, carsten.dominik@gmail.com
Subject: Re: org-capture and XEmacs, indenting too far
Date: Sun, 23 Oct 2011 10:15:51 +0200	[thread overview]
Message-ID: <y9lwrbwgm2w.fsf@deinprogramm.de> (raw)
In-Reply-To: <y9lipnhjd8w.fsf@deinprogramm.de> (Michael Sperber's message of "Sat, 22 Oct 2011 16:46:07 +0200")

Michael Sperber <sperber@deinprogramm.de> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>> Hi, I'm using XEmacs 21.5  (beta29) "garbanzo" d27c1ee1943b+ [Lucid]
>> (i686-pc-cygwin, Mule) of Mon Oct 18 2010 on RPluim, with the following
>> org-capture-templates
>> (("t" "Todo" entry (file+headline "~/org/notes.org" "Tasks") "* TODO %?"))
>> The problem is that for some reason the resulting TODO heading is has 2
>> extra spaces, and is placed at too deep a level, giving:
>> * Tasks
>> ***   TODO a task
>> I've tested this on a fairly recent emacs24 build, and everything works
>> fine there, so this is probably something XEmacs specific.  Can anyone
>> suggest any way to track this down (I'd bisect, but I've yet to find a
>> 'good' version)?
> I finally got around to looking into this: The reason is that, in
> org-capture mode, `outline-level' is bound to outline.el's function,

Looking at this again, my analysis was stupid: The problem is that the
indirect buffer used for capture is not in org-mode at all, and that is
indeed an XEmacs-specific problem, as `make-indirect-buffer' does not
accept the 'clone argument on XEmacs.  I therefore retract the rubbish I
sent earlier and suggest this one instead:

diff --git a/lisp/ob-calc.el b/lisp/ob-calc.el
index 14d7d5d..44ed82b 100644
--- a/lisp/ob-calc.el
+++ b/lisp/ob-calc.el
@@ -28,7 +28,6 @@
 ;;; Code:
 (require 'ob)
 (require 'calc)
-(require 'calc-store)
 (unless (featurep 'xemacs)
   (require 'calc-trail)
   (require 'calc-store))
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index e1b8a4f..fa9895f 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -848,6 +848,7 @@ it.  When it is a variable, retrieve the value.  Return whatever we get."
   (goto-char (org-capture-get :pos))
   (org-set-local 'org-capture-target-marker
 		 (move-marker (make-marker) (point)))
+  (org-set-local 'outline-level 'org-outline-level)
   (let* ((template (org-capture-get :template))
 	 (type (org-capture-get :type)))
     (case type
@@ -1213,7 +1214,10 @@ Use PREFIX as a prefix for the name of the indirect buffer."
       (setq bname (concat prefix "-" (number-to-string (incf n)) "-" base)))
     (condition-case nil
         (make-indirect-buffer buffer bname 'clone)
-      (error (make-indirect-buffer buffer bname)))))
+      (error 
+       (let ((buf (make-indirect-buffer buffer bname)))
+	 (with-current-buffer buf (org-mode))
+	 buf)))))
 (defun org-capture-verify-tree (tree)

Sorry about the snafu.

Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla

  reply	other threads:[~2011-10-23  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 10:09 org-capture and XEmacs, indenting too far Robert Pluim
2011-10-22 14:46 ` Michael Sperber
2011-10-23  8:15   ` Michael Sperber [this message]
2011-10-23  9:54     ` Carsten Dominik
2011-10-23 17:53     ` Bastien
2011-10-26 17:43     ` Bastien
2011-10-26 17:50   ` [Accepted] " Bastien Guerry

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=y9lwrbwgm2w.fsf@deinprogramm.de \
    --to=sperber@deinprogramm.de \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpluim@gmail.com \


* 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


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).