[O] Rebuilding the Agenda hides inline Images
Hello Org-mode developers, I have an org document with some inline images that I'd like to be displayed permanently. I can switch them on using org-toggle-inline-images, but whenever the agenda is rebuilt, either manually or by an idle timer, they disappear, so I have to call org-toggle-inline-images twice (switch inline images off, then on again ) to get them back. I have found no clues in the manual or mailing list for this being the intended behavior, so I guess I found a bug. Ciao, Marcus Klemm
Re: [O] Local subtree view
Rebel Neurofog rebelneuro...@gmail.com writes: Hello, Rebel! I'm finally beginning to integrate Org mode into my way of thinking. But one thing really bothers me: local subtree view. The closest thing I'd like to have is (org-tree-to-indirect-buffer), ... Second, I'd rather edit selected subtree in local mode and then go back to global (normal) mode instead of dealing with 2 windows. Have you considered M-x org-narrow-to-subtree? You can use M-x widen to get back to the full view. Sacha Chua
[O] Ask for feature: include other .org files from a (main) .org file
I want to place some customization codes in a separate file, and include it from other files later. For example, file config.org has a single line #+MATHJAX: align:left mathml:t. How do I include it in another .org file abc.org so that the net-effect is exactly same as I write that #+MATHJAX line directly in abc.org (#+INCLUDE doesn't meet this requirement)? Thanks. -- Regards, Zihan, Sheldon Liu The Media Computing Group (MCG) where Media Spectrum unleashes Digital Potential for Fun in Life. School of Creative Media (SCM) City University of Hong Kong
Re: [O] alignment of description list in Org and export old and new
Hi all 2012-06-02 Michael Brand michael.ch.br...@gmail.com: [...] - cmd --log-level=wrn -o dst src :: long term + long descr bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla [...] M-q on the item long term + long descr that is aligned manually as shown first will be stable only after a second M-q instead of already after the first M-q with release_7.8.10-633 on 23.3.1. The attached patch resolves also the above issue: Description list: improve regexp consistency * lisp/org-list.el (org-at-item-description-p, org-list-item-body-column): Make the inline regexp more consistent with `org-list-full-item-re', the inline regexp Description list items from `org-set-font-lock-defaults and others'. This resolves some issues with M-q (org-fill-paragraph) on description lists. Michael From 6f642be9974cf153f636a2f3870f63502203fe13 Mon Sep 17 00:00:00 2001 From: Michael Brand michael.ch.br...@gmail.com Date: Sun, 10 Jun 2012 18:35:39 +0200 Subject: [PATCH] Description list: improve regexp consistency * lisp/org-list.el (org-at-item-description-p, org-list-item-body-column): Make the inline regexp more consistent with `org-list-full-item-re', the inline regexp Description list items from `org-set-font-lock-defaults and others'. This resolves some issues with M-q (org-fill-paragraph) on description lists. --- lisp/org-list.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org-list.el b/lisp/org-list.el index 648497f..c6dcb79 100644 --- a/lisp/org-list.el +++ b/lisp/org-list.el @@ -489,7 +489,7 @@ group 4: description tag) (defun org-at-item-description-p () Is point at a description list item? - (org-list-at-regexp-after-bullet-p \\(\\S-.+\\)[ \t]+::[ \t]+)) + (org-list-at-regexp-after-bullet-p \\(\\S-.+\\)[ \t]+::\\([ \t]+\\|$\\))) (defun org-at-item-checkbox-p () Is point at a line starting a plain-list item with a checklet? @@ -2035,7 +2035,7 @@ Possible values are: `folded', `children' or `subtree'. See (let (bpos bcol tpos tcol) (save-excursion (goto-char item) - (looking-at [ \t]*\\(\\S-+\\)\\(.*[ \t]+::\\)?[ \t]+) + (looking-at [ \t]*\\(\\S-+\\)\\(.*[ \t]+::\\)?\\([ \t]+\\|$\\)) (setq bpos (match-beginning 1) tpos (match-end 0) bcol (progn (goto-char bpos) (current-column)) tcol (progn (goto-char tpos) (current-column))) -- 1.7.4.2
Re: [O] [ANN] Org Elements in contrib
Hi Nicolas On Mon, Nov 21, 2011 at 7:50 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: I've added org-element.el in contrib directory. It is a complete parser and interpreter for Org syntax. [...] the following code will parse the buffer, interpret the parsed tree, and create a canonical copy of it (no indentation, lowercased blocks, standard keywords): #+begin_src org (let ((out (org-element-interpret-data (org-element-parse-buffer (switch-to-buffer (get-buffer-create *Bijectivep*)) (erase-buffer) (insert out) (goto-char (point-min)) (org-mode)) #+end_src [...] Feedback is welcome. Good to mention is also this code to show the pretty print formatted lisp object representation of the current Org buffer: #+BEGIN_SRC emacs-lisp (let ((out (org-element-parse-buffer))) (setq eval-expression-print-length nil) (setq eval-expression-print-level nil) (switch-to-buffer (get-buffer-create *prettyprint*)) (erase-buffer) (insert (pp-to-string out)) (goto-char (point-min)) (emacs-lisp-mode) (setq truncate-lines t)) #+END_SRC Not sure if the following should be supported by org-element-interpret-data: #+BEGIN_SRC org ,variable declaration in some programming languages: ,- Perl :: the variable declaration can be implicit ,- C :: , #+BEGIN_SRC C ,time_t variable_name; , #+END_SRC #+END_SRC The above command for Bijectivep of (org-element-interpret-data (org-element-parse-buffer)) shows BEGIN_SRC on the same line as - C :: but I expect it on a separate line like in the original. The above command for prettyprint of (org-element-parse-buffer) alone looks ok to me. Michael
Re: [O] date added into logbook?
On May 31, 2012, at 8:03 PM, Sacha Chua wrote: Have you considered using org-capture with the clock options? I like using this because it automatically grabs the timestamp as well, and when I press C-c C-c, it clocks out. Handy - I've been using it to calculate my words per minute (dismally low for blog posts sometimes!). Here's a snippet from my config: snip I would eventually love to have better access to the existing framework for logbook entries, but I think using org-capture seems the way to go for now. Thank you (and others) very much. — Michael
Re: [O] Ask for feature: include other .org files from a (main) .org file
Never mind. I just noticed that #+setupfile is what I want. Thx. On Sun, Jun 10, 2012 at 8:23 PM, Zihan, Sheldon Liu updog...@gmail.comwrote: I want to place some customization codes in a separate file, and include it from other files later. For example, file config.org has a single line #+MATHJAX: align:left mathml:t. How do I include it in another .org file abc.org so that the net-effect is exactly same as I write that #+MATHJAX line directly in abc.org (#+INCLUDE doesn't meet this requirement)? Thanks. -- Regards, Zihan, Sheldon Liu The Media Computing Group (MCG) where Media Spectrum unleashes Digital Potential for Fun in Life. School of Creative Media (SCM) City University of Hong Kong -- Regards, Zihan, Sheldon Liu The Media Computing Group (MCG) where Media Spectrum unleashes Digital Potential for Fun in Life. School of Creative Media (SCM) City University of Hong Kong
Re: [O] Smart Quotes Exporting
Nicolas Goaziou n.goaziou at gmail.com writes: Hello, Mark E. Shoulson mark at kli.org writes: Update on the smart-quotes patch. Supports the odt exporter now too, which I think covers all the current major new exporters for which it is relevant (adding smart quotes to ASCII export is a contradiction in terms; ASCII exporter also handle UTF-8. So it's good to have there too. Really? I would have thought ASCII meant ASCII, as in 7-bit clean text. More of a plain text exporter then. Fair enough. I'll work it in. should it be in the publish exporter? It didn't look like it to me). No. OK, good. Added an options keyword, '' (that is, the double-quote mark) to select smart quotes on/off, and a defcustom for customizing your default. Set the default default [sic] to nil, though actually it might be reasonable to set it to t. Slight touch-up to the regexps since last time, but they will definitely be subject to a lot of fine-tuning as more special cases are found that break them and ways to fix it are found (the close-quote still breaks on one of /a/. or /a./) Again, using regexps on plain text objects is a wrong approach, as you need a better understanding of the whole paragraph structure to properly. I already suggested a possible solution, is there anything wrong with it? It looked to me like your solution would essentially boil down to do string handling when there's a string, otherwise recur down and find the strings, which essentially means apply it to all the strings... and there were already functions out there applying things to strings, so this can just ride along with them. Here, let's look at your suggestion and see if we can find what I missed: ] Walk element/object/secondary-string's contents . ] ] 1. When a string is encountered: ] ] 1. If it has a quote as its first or last position, check for ] objects before or after the string to guess its status. An ] object never starts with a white space, but you may have to ] check :post-blank property in order to know if previous object ] had white spaces at its end. ] ] 2. For each quote everywhere else in the string, your regexp can ] handle it fine. ] ] 2. When an object belonging to `org-element-recursive-objects' is ] encountered, apply the function to this object. ] ] 3. Accumulate returned strings or objects. So, if it's a string, use the regexps (if they can be smart enough to look at beginning and end of the string, which they can--though I haven't been using the :post-blank property so presumably something is amiss), and if it isn't a string, recur down until you get to a string... Ah, but only if it's in org-element-recursive-objects. So the issue with the current state is that it would wind up applying to too much? (it would hit code and verbatim elements, for example, and that would be wrong.) And detecting such things at the string level would be the wrong place... So it remains to find the right place in the processing to put a function like the one you describe. I'm trying to get a proper understanding of the code structure to see what you mean. Looks like it should be something like a transcoder, only called on everything... wait, called on the top-level parsed tree object, recursively doing its thing before(?) the transcoders of the individual objects get to it. So almost something replacing the (lambda (blob contents info) contents) stub in org-export-transcoder; does that make sense to you? Otherwise, called somehow in org-export-data. In either case made a hook of some kind so that it is backend-specific. Does it sound like I am understanding this right, to you? The on-screen one would still use the plain-string computation, as you said, since the full parse isn't available. And that seems to work okay (the export works okay too, for simple cases.) It would also need to be tweaked not to act on verbatim/comment text, etc. Thanks, ~mark
