[O] My attempt of org babel inline src block highlighting
Hi, I just naively modified org-fontify-drawers to fontify org babel inline src block. The result looks reasonable to me. I put these two functions in a src block in my org file and executed it, then refreshed display with M-x org-mode. (defun org-fontify-inline-src-block (limit) Fontify inline source block. (when (re-search-forward org-babel-inline-src-block-regexp limit t) (add-text-properties *(match-beginning 1*) (match-end 0) '(font-lock-fontified t face (t (:foreground #008ED1 :background #EA (org-remove-flyspell-overlays-in (match-beginning 0) (match-end 0)) t)) (defun org-set-font-lock-defaults () .. ;; Drawers '(org-fontify-drawers) * ;; Inline source block* * '(org-fontify-inline-src-block)* Cheers, Bowen
Re: [O] My attempt of org babel inline src block highlighting
Hello, Bowen Li wrote: I just naively modified org-fontify-drawers to fontify org babel inline src block. The result looks reasonable to me. I put these two functions in a src block in my org file and executed it, then refreshed display with M-x org-mode. (defun org-fontify-inline-src-block (limit) Fontify inline source block. (when (re-search-forward org-babel-inline-src-block-regexp limit t) (add-text-properties *(match-beginning 1*) (match-end 0) '(font-lock-fontified t face (t (:foreground #008ED1 :background #EA (org-remove-flyspell-overlays-in (match-beginning 0) (match-end 0)) t)) (defun org-set-font-lock-defaults () .. ;; Drawers '(org-fontify-drawers) * ;; Inline source block* * '(org-fontify-inline-src-block)* I may have missed obvious things, but I don't understand which problem you are trying to resolve. Could you elaborate, please? Best regards, Seb -- Sebastien Vauban
Re: [O] publishuing in html5
Nicolas, 2013/12/15 Nicolas Goaziou n.goaz...@gmail.com Hello, Catonano caton...@gmail.com writes: I made a temporary repository here https://github.com/humanitiesNerd/exploring-org-mode in case anyone wants to take a look In configuration.el you use :org-html-html5-fancy 1 but it should be :html-html5-fancy 1 Regards, -- Nicolas Goaziou thank you so much for your suggestion ! I tried but it still doesn't work. That is, this block #+ATTR_HTML: :controls controls :width 350 #+BEGIN_VIDEO #+HTML: source src=movie.mp4 type=video/mp4 #+HTML: source src=movie.ogg type=video/ogg Your browser does not support the video tag. #+END_VIDEO gets translated to div controls=controls width=350 class=video source src=movie.mp4 type=video/mp4 source src=movie.ogg type=video/ogg p Your browser does not support the video tag. /p /div As for my versions of Org-mode, Emacs and operating system, I'm gonna write about it in a minute Thanks again
Re: [O] new odt-exporter: problems with formatting in captions
J == Jambunathan K kjambunat...@gmail.com writes: J NOTE: If someone knows how to accommodate short captions (so that an J that an Index/TOC could be generated from within LibreOffice based on J it, please let me know.) The openDocument standard says in 7.4.1 Use Caption Each object contained in a text document has a name. In addition, images also have a caption. The image caption or the image name can be gathered for the index of illustrations. define name=text-illustration-index-source-attrs combine=interleave optional attribute name=text:use-caption a:defaultValue=true ref name=boolean/ /attribute /optional /define Looks to me like one should have #+NAME and #+CAPTION in the org file, I'd consider the former a candidate for the short caption. HTH, Martin
Re: [O] publishuing in html5
Nick, 2013/12/14 Nick Dokos ndo...@gmail.com Catonano caton...@gmail.com writes: 2013/12/11 Nicolas Goaziou n.goaz...@gmail.com What OS? What version of emacs? Are you sure you are not picking up the org-mode bits that are bundled with emacs? The following file (which I posted before) --8---cut here---start-8--- #+HTML_DOCTYPE: html5 #+OPTIONS: html5-fancy:t #+BEGIN_ASIDE Lorem Ipsum #+END_ASIDE --8---cut here---end---8--- Admittedly I haven't tested this suggestion of yours. Because I'd like to avoid writing such stuff in each and every file. Ideally I should be producing a blog with this so there should be several files. Not sure why it says 8.2.3c - I'm running: Org-mode version 8.2.4 (release_8.2.4-340-g059dc0 @ /home/nick/elisp/org-mode/lisp/) Package: Org-mode version 8.2.4 (release_8.2.4-321-g0eb020 @ /home/catonano/.emacs.d/el-get/org-mode/lisp/) GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of 2013-07-14 on pierrot Emacs : GNU Emacs 24.3.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.8.2) of 2013-08-14 on buildvm-15.phx2.fedoraproject.org So both my Emacs and org-mode are older than yours. I installed Emacs with the standard Fedora package management machinery and org-mode with el-get Linux pierrot 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Linux xps 3.11.9-200.fc19.x86_64 #1 SMP Wed Nov 20 21:22:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Re: [O] publishuing in html5
Hello, Catonano caton...@gmail.com writes: I tried but it still doesn't work. That is, this block #+ATTR_HTML: :controls controls :width 350 #+BEGIN_VIDEO #+HTML: source src=movie.mp4 type=video/mp4 #+HTML: source src=movie.ogg type=video/ogg Your browser does not support the video tag. #+END_VIDEO gets translated to div controls=controls width=350 class=video source src=movie.mp4 type=video/mp4 source src=movie.ogg type=video/ogg p Your browser does not support the video tag. /p /div As specified already in this thread, you also need :html-doctype html5 in your configuration. Regards, -- Nicolas Goaziou
Re: [O] [export] org-export-with-* bugs
Hello, Aaron Ecay aarone...@gmail.com writes: 2013ko abenudak 17an, Nicolas Goaziou-ek idatzi zuen: The more I look at it, the more I'm inclined to think that it's totally useless. I don't think anyone wants tables removed from Org syntax. Though, occasionally some line starting with | can be interpreted as a table. In this case, it's possible to use \vert entity anyway. I'm not sure it is worth fixing. I think we really should remove it, or change its meaning, like |:nil means that all tables are ignored in export process (which is probably almost as useless). The same goes for ::nil. I think either suggestion (total removal or changing semantics) is a reasonable option. I'll ask the question in a separate thread. (fixed-width is one of the branches in the ‘case’ form in the new code...?) Indeed. I attached the draft, not the real patch. I committed the latter. I can confirm the fix. It looks like the new mechanism is equivalent to a parse tree filter. It is exactly a parse tree filter. Should org-export--remove-uninterpreted be added to the default value of org-export-filter-parse-tree-functions, rather than hard-coding it into org-export-as? No, it shouldn't. `org-export-filter-parse-tree-functions' is meant for user's consumption. For example, export back-end have their own way to add such a filter without clobbering the variable. In this case, the implemented behaviour is clearly not optional, so it is logically hard-coded. Thank you for reporting the problem. Regards, -- Nicolas Goaziou
Re: [O] [RFC] [patch] open/delete attachment with inherited directory
Hello, Aaron Ecay aarone...@gmail.com writes: Hmm, good catch. Perhaps then we should read the property if it exists, but fall back to querying the filesystem in case it does not. WDYT? I didn't test it, but there might be a problem if a file name contains white spaces. If there isn't, it doesn't hurt to provide this alternative way to get attached files (and `org-attach-file-list-property' need to mention it). Otherwise, I think there are too many limitations in this patch to be worth applying. Regards, -- Nicolas Goaziou
[O] Agenda view: do not display tasks of projects scheduled in the future
Hello, I would like to tweak my agenda views such that tasks belonging to projects scheduled in the future are not shown. I've searched a bit about this and I found out that deadlines and schedules are not inherited, so that approach would not work. I'm thus trying to tweak a custom skip function to jump over any headline scheduled for the future. I looked into org.el but could not find a way to write a predicate org-entry-scheduled-in-future-p that is true when an entry is scheduled in the future. I would use it for the following skipping command: #+BEGIN_SRC emacs-lisp (defun as/skip-future-tasks () Skip future tasks (save-restriction (widen) (let ((subtree-end (save-excursion (org-end-of-subtree t (cond ((org-entry-scheduded-in-future-p) subtree-end) (t nil) #+END_SRC Any suggestion as how I might write such a predicate? Thanks, Alan
Re: [O] [parser] subscripts and underlines interacting badly
Hello,
Aaron Ecay aarone...@gmail.com writes:
The attached patch implements this. It also updates the fontification
to match (by calling out to the parser, so there are potential
performance issues although with the cache it will hopefully not be an
issue in practice), and notes the new heuristic in the manual. The test
suite passes.
Thank you. Here are some comments and the usual nitpicks.
From e2044312b95f8b427ddc662cd1abf10bf4d87b2d Mon Sep 17 00:00:00 2001
From: Aaron Ecay aarone...@gmail.com
Date: Sun, 15 Dec 2013 21:30:27 -0500
Subject: [PATCH] org-element: use brackets to disambiguate subscript/underline
You need a capital after colon.
* lisp/org-element.el (org-element-sub/superscript-successor): use
brackets to disambiguate subscript/underline
Ditto, and a period at the end of the sentence.
* lisp/org.el (org-do-emphasis-faces): incorporate the above
disambiguation
I'd rather not use `org-element-context' in fontification ATM. My plan
is, indeed, to use the parser for fontification, but in a planned-out
way. Doing it too early may be counter-productive.
For now, we can accept some discrepancies between fontification and
syntax (there are many other such occurrences anyway).
* doc/org.texi: reflect these changes in the manual
See above.
+When it follows an alphanumeric character, the underscore is always
+interpreted as a subscript (@pxref{Subscripts and superscripts}), and when it
+follows whitespace it is always the start of an underline (assuming a
+matching underscore is found in a proper position further along). However,
+after a punctuation character (for example the apostrophe), the underscore
+character can be ambiguous between these two interpretations. Org uses a
+simple heuristic for these cases: if the character following the underscore
+is an opening brace @samp{@{} or if no matching underscore is seen in the
+following text, the underscore is considered to be the start of a subscript.
+Otherwise, it is the start of underlining.
There is no harm in documenting it, but remember that it's not a feature
of the syntax. Maybe it could be shortened and put into a footnote
instead?
+(let (res)
+ (while (and (not res)
+ (re-search-forward org-match-substring-regexp nil t))
+ (goto-char (match-beginning 0))
+ (when (or
+;; this subscript uses brackets - handle as subscript
+;; unconditionally
Comments need to start with a capital and end with a period.
+(eq (aref (match-string 3) 0) ?{)
+;; it is not ambiguous with an underline - handle as
+;; subscript
+(not (looking-at-p org-emph-re)))
It should be `org-looking-at-p' for compatibility with other Emacsen.
+ (setq res (cons (if (string= (match-string 2) _)
+ 'subscript
+ 'superscript)
+ (match-beginning 2
+ ;; otherwise - keep going, and let the underline
+ ;; parser have it
+ (goto-char (match-end 0)))
I think
(save-excursion (goto-char (match-beginning 0)) ...)
is better than
(goto-char (match-beginning 0)) ... (goto-char (match-end 0)).
+ res)))
I suggest to use (catch 'found ... (throw 'found (cons ...))) instead
of RES variable: the less `setq', the better.
Regards,
--
Nicolas Goaziou
Re: [O] publishuing in html5
Catonano caton...@gmail.com writes: 2013/12/14 Nick Dokos ndo...@gmail.com The following file (which I posted before) --8---cut here---start-8--- #+HTML_DOCTYPE: html5 #+OPTIONS: html5-fancy:t #+BEGIN_ASIDE Lorem Ipsum #+END_ASIDE --8---cut here---end---8--- Admittedly I haven't tested this suggestion of yours. Because I'd like to avoid writing such stuff in each and every file. Ideally I should be producing a blog with this so there should be several files. I'm not suggesting that you write this stuff in each and every file in your blog. I'm just suggesting that before you can even have a blog (at least using this mechanism), you have to first figure out what the problem is and resolve it. Then you can optimize. If the above works, then it's straigthforward to translate this into settings that you can put into your .emacs. If it doesn't, anything else you or we do is wasted effort (of which there's been plenty in this thread). Nick
Re: [O] #+TEXT: disappeared
On Tue, 17 Dec 2013 15:53:25 +0100 Sebastien Vauban sva-n...@mygooglest.com wrote: Manfred Lotz wrote: I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? IIUC, it became `#+ascii:'. Best regards, Seb Hm, when I try this it won't even appear in the .tex file. -- Manfred
[O] org2blog problems.
I have been attempting to use emacs org2blog but am now consistently getting this error report - Contacting host: www.sharons.org.uk:80 xml-rpc-xml-to-response: XML-RPC fault `Incorrect username or password.' I'm using '.netrc' and this is - machine host100 myblog A taste of linux login boudiccas password rhubarbandcustard This is the relevant sections in my .emacs - (setq load-path (cons ~/.emacs.d/elpa/org2blog-20130707.323 load-path)) ;; depends on netrc, xml-rpc (require 'netrc) (require 'xml-rpc-autoloads) (require 'org2blog-autoloads) (require 'metaweblog) ;; load the entry 'A taste of linux' in the ~/.netrc, we obtain a hash-map with the needed data ;; now enter the data in the org2blog list of blogs (require 'netrc) ;; or nothing if already in the load-path (setq blog (netrc-machine (netrc-parse ~/.netrc) A taste of linux t)) (setq org2blog/wp-blog-alist '((A taste of linux :url http://www.sharons.org.uk/xmlrpc.php; :username (netrc-get blog login) :password (netrc-get blog password (add-hook 'org-mode-hook 'org2blog/wp-mode) Why cant I log on with org2blog please? Is it because either .netrc or org2blog have a maximum password length please? That’s the only thing that I can think of as to why it is consistently failing. Sharon. -- A taste of linux = http://www.sharons.org.uk efever = http://www.efever.blogspot.com/ efever = http://sharon04.livejournal.com/ my git repo = https://bitbucket.org/boudiccas/dots Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.3.2 Registered Linux user 561944 signature.asc Description: PGP signature
Re: [O] org2blog problems.
Sharon Kimble boudic...@talktalk.net writes: I have been attempting to use emacs org2blog but am now consistently getting this error report - Contacting host: www.sharons.org.uk:80 xml-rpc-xml-to-response: XML-RPC fault `Incorrect username or password.' ... Why cant I log on with org2blog please? Is it because either .netrc or org2blog have a maximum password length please? That’s the only thing that I can think of as to why it is consistently failing. Punchagan (the author of org2blog) occasionally appears on this mailing list, but given that you didn't get an answer the first time you asked the question, he seems not to be watching ATM. You might have better luck contacting him through github. In any case, the problem you are having has nothing to do with org, so unless somebody else here happens to be using org2blog and has the inclination to help, you are likely to be disappointed in getting an answer here. Not meaning to discourage you: just setting expectations. Nick
Re: [O] #+TEXT: disappeared
Hello, Manfred Lotz manfred.l...@arcor.de writes: On Tue, 17 Dec 2013 15:53:25 +0100 Sebastien Vauban sva-n...@mygooglest.com wrote: Manfred Lotz wrote: I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? IIUC, it became `#+ascii:'. Best regards, Seb Hm, when I try this it won't even appear in the .tex file. TEXT keywords were removed in Org 8 because we do not need them anymore. Would you mind providing your use case, or, better, an example, so we can help you? Regards, -- Nicolas Goaziou
Re: [O] #+TEXT: disappeared
Manfred Lotz manfred.l...@arcor.de writes: On Tue, 17 Dec 2013 15:53:25 +0100 Sebastien Vauban sva-n...@mygooglest.com wrote: Manfred Lotz wrote: I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? IIUC, it became `#+ascii:'. Best regards, Seb Hm, when I try this it won't even appear in the .tex file. I'm not sure what your expectations might be, but if you want to add special code to a .tex file, Section 12.7.3 of the manual, Quoting LaTeX code, describes how to do that. hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Bug: Bad ODT files when including multiple images [7.9.3f (release_7.9.3f-17-g7524ef at /usr/share/emacs/24.3/lisp/org/)]
The fix is available in private repository: http://repo.or.cz/w/org-mode/org-kjn.git As far as schema validation with .rnc files go, draw:name is an optional attribute of draw:frame. So, I am not sure why LibreOffice is insisting on draw:name to exist and be unique. Due to the above issue, I have also retired the support for short-caption. See my not pertaining to LibreOffice upgrades here: http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00477.html Due to this issue, I proposed that I maintain ox-odt.el right within Emacs bzr repo. Unfortunately, it resulted in some heated exchanges. http://lists.gnu.org/archive/html/emacs-devel/2013-12/msg00509.html To the people who rely on ODT exporter for their day to day use and want it as part of Emacs 1. Find someone with Copyright Assignment to fix the critical issue(s). 2. Write to Gnu/Linux distributors - Debian, Gentoo etc - and persuade them to apply patches from my private repo before building the org-mode or Emacs deb packages. Download the files. Don't use git. The files relevant to ODT are 1. lisp/ox-odt.el 2. etc/styles 3. etc/schema 4. contrib/lisp/ox-jabref.el (3) above is optional. (4) is needed if you need export citations with JabRef. Tim wiskey5al...@gmail.com writes: Let me upgrade my LibreOffice and report back. Jambunathan, was wondering if you had a chance to look at this error ? I can confirm it is an issue on my Ubuntu 13.10 system with : - emacs 24.3.1 - org-mode 8.2.4 (org-plus-contrib elpa package 20131216) - libreoffice 4.1.3.2 I use the odt export to create student handouts and *really* don't want to go back through 200+ documents to add captions to all of the images ! Thanks -Tim
[O] Warning (initialization): Your `load-path' seems to contain your `.emacs.d' directory
I am an emacs and org-mode newbie. I am mainly coming to Emacs for Org-Mode. So am using Eric Schulte's Emacs Starter Kit 24. I put this in .emacs.d. It is suggested in the kit Move the resulting directory to ~/.emacs.d http://eschulte.github.io/emacs24-starter-kit/#fn.1 http://eschulte.github.io/emacs24-starter-kit/ When I start Emacs I get the following error. Warning (initialization): Your `load-path' seems to contain your `.emacs.d' directory: /home/username/.emacs.d/ This is likely to cause problems... Consider using a subdirectory instead, e.g.: /home/username/.emacs.d/lisp I am uncertain how I should proceed now. I suspect this will be a common problem for new people. How should I setup the Emacs Starter Kit? Move the whole kit to /home/username/.emacs.d/lisp ? Put the init.el in .emacs.d? Regards, Paul Harper -- about.me/pauljamesharper Women and cats will do as they please, and men and dogs should relax and get used to the idea. Robert Heinlein
Re: [O] Warning (initialization): Your `load-path' seems to contain your `.emacs.d' directory
Thanks. I had seen that thread but it is still unclear to me what that means. I just found this which has some discussion from Eric Schulte himself. https://lists.gnu.org/archive/html/emacs-orgmode/2013-04/msg01777.html I'll have to go and read this. If I get a solution I'll make sure I post it. Regards, Paul On 19 December 2013 02:31, Jambunathan K kjambunat...@gmail.com wrote: Paul Harper harper.pau...@gmail.com writes: Warning (initialization): Your `load-path' seems to contain your `.emacs.d' directory: /home/username/.emacs.d/ This is likely to cause problems... Consider using a subdirectory instead, e.g.: /home/username/.emacs.d/lisp (I know nothing about starter kit) On a related note, this warning occurs with Emacs from bzr trunk. The problem surfaced in the help list. See http://permalink.gmane.org/gmane.emacs.help/94823 -- about.me/pauljamesharper Women and cats will do as they please, and men and dogs should relax and get used to the idea. Robert Heinlein
[O] [RFC] About `org-export-with-\(fixed-width\|tables\)'
Hello, At the moment, `org-export-with-fixed-width' and `org-export-with-tables' (or their OPTIONS equivalent ::t and |:t) are broken when not set to their default value. Also, fixing them is not trivial. I think this is a good time to ponder about their usefulness. Indeed, I don't think anyone would want to remove tables (or fixed-width areas) from Org syntax. These variables were probably written because tables and fixed-width can occasionally get in the way, on very specific lines. However, Org already provides ways to work around such problems. For example, a table can be wrapped within an example block, or an offending line can start with \vert instead of |. Therefore, in today's Org, they don't make much sense anymore. As a consequence, I'd like to either: 1. Remove them completely from code base; 2. Change their meaning so they behave like `org-export-with-toc' or `org-export-with-tags', that is: when `org-export-with-tables' is set to nil, all tables are ignored during export. I don't think option 2 is really useful, but I don't mind either way. WDYT? Regards, -- Nicolas Goaziou
Re: [O] [RFC] About `org-export-with-\(fixed-width\|tables\)'
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, At the moment, `org-export-with-fixed-width' and `org-export-with-tables' (or their OPTIONS equivalent ::t and |:t) are broken when not set to their default value. Also, fixing them is not trivial. I think this is a good time to ponder about their usefulness. Indeed, I don't think anyone would want to remove tables (or fixed-width areas) from Org syntax. These variables were probably written because tables and fixed-width can occasionally get in the way, on very specific lines. However, Org already provides ways to work around such problems. For example, a table can be wrapped within an example block, or an offending line can start with \vert instead of |. Therefore, in today's Org, they don't make much sense anymore. As a consequence, I'd like to either: 1. Remove them completely from code base; AFAIAC, they can go. 2. Change their meaning so they behave like `org-export-with-toc' or `org-export-with-tags', that is: when `org-export-with-tables' is set to nil, all tables are ignored during export. I don't think option 2 is really useful, but I don't mind either way. WDYT? Nick
Re: [O] [RFC] About `org-export-with-\(fixed-width\|tables\)'
Nicolas Goaziou n.goaz...@gmail.com writes: 1. Remove them completely from code base; Fine with me. If needing to treat a region in a special way it's more clear to explicitly state it IMO. –Rasmus -- A clever person solves a problem. A wise person avoids it
Re: [O] [RFC] About `org-export-with-\(fixed-width\|tables\)'
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, At the moment, `org-export-with-fixed-width' and `org-export-with-tables' (or their OPTIONS equivalent ::t and |:t) are broken when not set to their default value. Also, fixing them is not trivial. I think this is a good time to ponder about their usefulness. Indeed, I don't think anyone would want to remove tables (or fixed-width areas) from Org syntax. These variables were probably written because tables and fixed-width can occasionally get in the way, on very specific lines. However, Org already provides ways to work around such problems. For example, a table can be wrapped within an example block, or an offending line can start with \vert instead of |. Therefore, in today's Org, they don't make much sense anymore. As a consequence, I'd like to either: 1. Remove them completely from code base; Removal is fine with me. For years now, I've inserted the automatic boilerplate at the top of my Org mode documents, which has ::t and |:t. If the functions are removed, then it would be great if it wasn't necessary to go back and get rid of the obsolete OPTIONS in all those old, but still active, files. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] [RFC] About `org-export-with-\(fixed-width\|tables\)'
Hello, t...@tsdye.com (Thomas S. Dye) writes: Nicolas Goaziou n.goaz...@gmail.com writes: Removal is fine with me. For years now, I've inserted the automatic boilerplate at the top of my Org mode documents, which has ::t and |:t. If the functions are removed, then it would be great if it wasn't necessary to go back and get rid of the obsolete OPTIONS in all those old, but still active, files. For clarification, you needn't change old OPTIONS lines. It is the same as @:t in Org files written before 8.0: it doesn't mean anything anymore, but doesn't hurt either. Regards, -- Nicolas Goaziou
Re: [O] [RFC] Alternative to sub/superscript regexp
Completing myself,
OTOH, while we're at it, I wonder if we should keep grouping with
parenthesis. I guess that if you want to use parenthesis, you're going
to need math mode anyway, so there's no real need to make it easy to
type, e.g. :
x^(2-i)
which will become x$^\text{(2-i)}$ anyway.
I attach the suggested patch. I removed parenthesis-grouping for the
reasons I gave above. Carsten: if you'd rather keep this feature, let me
know, I'll provide another patch.
I also slightly changed the simplified regexp, as [:word:] includes
underscores in Org syntax. I used [:alnum:] instead.
Regards,
From ffda7d038326aececd9337850d4384e4fd207459 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou n.goaz...@gmail.com
Date: Wed, 18 Dec 2013 22:32:13 +0100
Subject: [PATCH] Change no brace sub/superscript syntax
* lisp/org.el (org-match-substring-regexp): Simplify syntax when not
using braces. Also remove parenthesis as grouping characters and make
the variable a defconst.
(org-match-substring-with-braces-regexp): Make the variable a defconst
and remove a useless group in regexp.
(org-use-sub-superscripts): Update docstring.
* lisp/org-element.el (org-element-subscript-parser,
org-element-superscript-parser): Adapt to group changes.
---
lisp/org-element.el | 17 -
lisp/org.el | 19 +++
2 files changed, 15 insertions(+), 21 deletions(-)
diff --git a/lisp/org-element.el b/lisp/org-element.el
index 31add7b..17062a9 100644
--- a/lisp/org-element.el
+++ b/lisp/org-element.el
@@ -3372,13 +3372,12 @@ Return a list whose CAR is `subscript' and CDR a plist with
Assume point is at the underscore.
(save-excursion
(unless (bolp) (backward-char))
-(let ((bracketsp (if (looking-at org-match-substring-with-braces-regexp)
- t
- (not (looking-at org-match-substring-regexp
+(looking-at org-match-substring-regexp)
+(let ((bracketsp (match-beginning 4))
(begin (match-beginning 2))
- (contents-begin (or (match-beginning 5)
+ (contents-begin (or (match-beginning 4)
(match-beginning 3)))
- (contents-end (or (match-end 5) (match-end 3)))
+ (contents-end (or (match-end 4) (match-end 3)))
(post-blank (progn (goto-char (match-end 0))
(skip-chars-forward \t)))
(end (point)))
@@ -3421,12 +3420,12 @@ Return a list whose CAR is `superscript' and CDR a plist with
Assume point is at the caret.
(save-excursion
(unless (bolp) (backward-char))
-(let ((bracketsp (if (looking-at org-match-substring-with-braces-regexp) t
- (not (looking-at org-match-substring-regexp
+(looking-at org-match-substring-regexp)
+(let ((bracketsp (match-beginning 4))
(begin (match-beginning 2))
- (contents-begin (or (match-beginning 5)
+ (contents-begin (or (match-beginning 4)
(match-beginning 3)))
- (contents-end (or (match-end 5) (match-end 3)))
+ (contents-end (or (match-end 4) (match-end 3)))
(post-blank (progn (goto-char (match-end 0))
(skip-chars-forward \t)))
(end (point)))
diff --git a/lisp/org.el b/lisp/org.el
index 59f55a8..4722714 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -882,7 +882,7 @@ will be parsed as single sub- or superscripts:
10^-12 or 10^-taua leading sign with digits or a word
x^2-y^3 will be read as x^2 - y^3, because items are
terminated by almost any nonword/nondigit char.
- x_{i^2} or x^(2-i)braces or parenthesis do grouping.
+ x_{i^2} braces do grouping.
Still, ambiguity is possible. So when in doubt, use {} to enclose
the sub/superscript. If you set this variable to the symbol `{}',
@@ -5636,21 +5636,18 @@ stacked delimiters is N. Escaping delimiters is not possible.
next (concat \\(?: nothing left next right \\)+ nothing)))
(concat left \\( re \\) right)))
-(defvar org-match-substring-regexp
+(defconst org-match-substring-regexp
(concat
\\(\\S-\\)\\([_^]\\)\\(
- \\( (org-create-multibrace-regexp { } org-match-sexp-depth) \\)
+ \\(?: (org-create-multibrace-regexp { } org-match-sexp-depth) \\)
\\|
- \\( (org-create-multibrace-regexp ( ) org-match-sexp-depth) \\)
- \\|
- \\(\\(?:\\*\\|[-+]?[^-+*!@#$%^_ \t\r\n,:\?~;./{}=()]+\\)\\)\\))
+ \\(?:\\*\\|[+-]?[[:alnum:].,\\]*[[:alnum:]]\\)\\))
The regular expression matching a sub- or superscript.)
-(defvar org-match-substring-with-braces-regexp
+(defconst org-match-substring-with-braces-regexp
(concat
- \\(\\S-\\)\\([_^]\\)\\(
- \\( (org-create-multibrace-regexp { } org-match-sexp-depth) \\)
- \\))
+ \\(\\S-\\)\\([_^]\\)
+ \\( (org-create-multibrace-regexp { } org-match-sexp-depth) \\))
The regular expression matching a sub- or superscript, forcing braces.)
(defun org-make-link-regexps ()
@@ -6087,8 +6084,6 @@ by a #.
(defvar org-latex-and-related-regexp nil
Regular expression for highlighting LaTeX, entities and sub/superscript.)
-(defvar org-match-substring-regexp)
-(defvar
Re: [O] [RFC] About `org-export-with-\(fixed-width\|tables\)'
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, t...@tsdye.com (Thomas S. Dye) writes: Nicolas Goaziou n.goaz...@gmail.com writes: Removal is fine with me. For years now, I've inserted the automatic boilerplate at the top of my Org mode documents, which has ::t and |:t. If the functions are removed, then it would be great if it wasn't necessary to go back and get rid of the obsolete OPTIONS in all those old, but still active, files. For clarification, you needn't change old OPTIONS lines. It is the same as @:t in Org files written before 8.0: it doesn't mean anything anymore, but doesn't hurt either. Perfect (as usual). Thanks! All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] org2blog problems.
Sharon Kimble boudic...@talktalk.net writes: I have been attempting to use emacs org2blog but am now consistently getting this error report - Contacting host: www.sharons.org.uk:80 xml-rpc-xml-to-response: XML-RPC fault `Incorrect username or password.' I'm using '.netrc' and this is - machine host100 myblog A taste of linux login boudiccas password rhubarbandcustard This is the relevant sections in my .emacs - (setq load-path (cons ~/.emacs.d/elpa/org2blog-20130707.323 load-path)) ;; depends on netrc, xml-rpc (require 'netrc) (require 'xml-rpc-autoloads) (require 'org2blog-autoloads) (require 'metaweblog) ;; load the entry 'A taste of linux' in the ~/.netrc, we obtain a hash-map with the needed data ;; now enter the data in the org2blog list of blogs (require 'netrc) ;; or nothing if already in the load-path (setq blog (netrc-machine (netrc-parse ~/.netrc) A taste of linux t)) (setq org2blog/wp-blog-alist '((A taste of linux :url http://www.sharons.org.uk/xmlrpc.php; :username (netrc-get blog login) :password (netrc-get blog password (add-hook 'org-mode-hook 'org2blog/wp-mode) Why cant I log on with org2blog please? Is it because either .netrc or org2blog have a maximum password length please? That’s the only thing that I can think of as to why it is consistently failing. From a very cursory reading, I'd say your .netrc is wrong - it should look like this: --8---cut here---start-8--- machine A taste of linux login boudiccas password rhubarbandcustard --8---cut here---end---8--- Untested and with no warranty, express, implied or otherwise - in particular I don't know if the spaces in the machine name cause problems. OTOH, I think netrc.el parses it correctly. And I hope that the password is either fictitious or you are going to change it asap. Nick
[O] How to get updates about new features in Orgmode
Hi, I am wondering whether there is a page in http://orgmode.org/ telling new features or updates in Orgmode? I keep updating my Org-mode from MELPA, but dunno what's going on or any new goodies just come. Thanks,Ha
[O] Exporting Agenda
I am trying to export the agenda and so far I can only export to html. The other formats (ps, pdf and ics) fail. Exports to ics ends up in an empty ics-file like this: BEGIN:VCALENDAR VERSION:2.0 X-WR-CALNAME:OrgMode PRODID:-//Johann Spies//Emacs with Org mode//EN X-WR-TIMEZONE:SAST X-WR-CALDESC: CALSCALE:GREGORIAN END:VCALENDAR The html file is good. ps and pdf exports fail totally with no output at all. When trying to use ics, ps and pdf exports I get Wrong type argument, stringp , nil I have the following in my .emacs (setq org-agenda-exporter-settings '((ps-number-of-columns 2) (ps-landscape-mode t) (org-agenda-add-entry-text-maxlines 5) (htmlize-output-type 'css))) I am using orgmode 8.2.1-1 on Debian with emacs24. What am I missing? Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
