[O] Tangling does not detect src blocks with capital BEGIN_SRC/END_SRC when case-fold-search nil

When tangling a file whose source code blocks have capitalized BEGIN_SRC and END_SRC (as produced by

Re: [O] new tag query parser [1/5] -- the motivating issues

Hi Martin, Assuming that org.el (with the new parser code) is byte-compiled, the performance difference is very minor. The only difference comes in converting the query string to a matcher form. The new parser has some additional overhead in function calls and keeping track of state, but in pra

Re: [O] full parser implementation for tag queries (parentheses, fast heading match, and more)

Hi Samuel, Thanks for your note. Just FYI, the earlier parser code in this thread has been superseded by the code in the post "new tag query parser [3/5]". The sexp input is a nice idea, and it would be very easy I think. The function org-make-tags-matcher now takes a query string but could

[O] new tag query parser [5/5] -- a (very) brief guide to the code

A few comments that might help navigate the new parser code in org-tag-query-parse.el. All diffs are relative to the 7.8.11 org.el. Let me know if you have any questions. * High Level Changes Two existing org functions are altered: 1. org-make-tags-matcher 2. org-scan-tags The changes t

[O] new tag query parser [4/5] -- a few ``illuminating'' examples

#+TITLE: New Tag Query Parser: A Few Illuminating Examples This post is structured as an org file with the example commands listed within. Copy this to a buffer and try the commands below on that buffer. * Preliminaries Point 207 The Point # labels on the headings give the point values for th

[O] new tag query parser [2/5] -- some bugs/limitations in the current parser

1. Property names with -'s are not handled properly Specifically, the escapes are not removed. Ex: (org-make-tags-matcher "PROP\\-WITH\\-HYPHENS=2") produces ("PROP\\-WITH\\-HYPHENS=2" and (progn (setq org-cached-props nil) (= (string-to-number (or (org-cached-ent

[O] new tag query parser [1/5] -- the motivating issues

My proposed changes in the tag query parser are motivated by the need and/or desire to do the following. (The example strings work with the new parser.) 1. Combine and modify tag queries programmatically. The leading case is that a function is given a tag query string and needs to *exclude*

[O] new tag query parser (re)introduction

At Bastien's urging, I'm (re)posting about my new tag query parser implementation in what I hope are clearer, more digestible, and more actionable pieces. My next few posts will be: 1. The motivating issues . 2. Some bugs/limitations in the current parser. 3. The new code and how to use/test

Re: [O] full parser implementation for tag queries (parentheses, fast heading match, and more)

Off to bed... -- Christopher On Sat, Aug 4, 2012 at 3:50 AM, Christopher Genovese wrote: > I am writing an application layer on top of org that uses the > entry mapping API, but I needed both negation of complex > selections and heading searches. Because the current tag query > parser does no

Re: [O] Four issues with org-babel-tangle

fort or the confusion with a functional directive that it would cause. I'll just suck it up and use the extra space. Thanks again, Eric. Best, Christopher On Thu, Sep 15, 2011 at 18:02, Eric Schulte wrote: > - Show quoted text - > Christopher Genovese writes: > > &g

[Orgmode] org-write-agenda failure

On Mac OS X 10.5.8, GNU Emacs 23.2.1, Org Mode 7.4, setting the following: (setq org-todo-keywords '((sequence "TODO" "WAIT" "DONE"))) (setq org-todo-keyword-faces '(("WAIT" . "lightgoldenrod2"))) has the intended effect, with WAIT items properly displayed, ... *until* I do org-write-agen