Re: [O] Macro question with new texinfo exporter
Hi Achim, Achim Gratz strom...@nexgo.de writes: I don't see the relation to the original problem, which is caused by a switch from master to maint. Yes, I realized this. I think that the current default, which has been in place for years, is just fine. Fair enough. Reloading uncompiled is only useful for when you want to create backtraces. ... which is why I always want, but users don't, I agree. Thanks, -- Bastien
[O] [ox-publish] index file empty?
Hallo, we are almost done migrating to the new exporter, currently the only showstopper is index generation, a feature we find very useful for our software documentation, here is an example generated with an older org version: http://www.nf.mpg.de/vinci3/doc/theindex.html We tried to locate the problem with Org-mode version 7.9.3e and it might be in ox-publish.el: org-publish-org-to seems to be called for each org file of our HTML publishing project, this is the only mention of org-publish-collect-index which is supposed to be installed as a parse tree filter. However, (if we are not mistaken) org-publish-collect-index is never called and this might be the reason why no index entries are generated. The only unusual comments in the message buffer are timestamp delimiter start was not found which might be cosmetic. Many thanks for any help with this. Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature
Re: [O] Macro question with new texinfo exporter
Bastien writes: Reloading uncompiled is only useful for when you want to create backtraces. ... which is why I always want, but users don't, I agree. We could provide org-reload-uncompiled that calls org-reload with a prefix argument, which would allow anyone so inclined to map C-c C-x ! to org-reload-uncompiled or another binding could be found. BTW, I just see that the menu entry for loading org uncompiled is wrong, it still tries to run it via C-u C-c C-x r, which isn't bound anymore since Org 6.26d due to a conflict with bindings in other modes. Looks like nobody ever used this in the last four years… fixed in maint and merged to master. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Macro question with new texinfo exporter
Achim Gratz strom...@nexgo.de writes: Bastien writes: Reloading uncompiled is only useful for when you want to create backtraces. ... which is why I always want, but users don't, I agree. We could provide org-reload-uncompiled that calls org-reload with a prefix argument, which would allow anyone so inclined to map C-c C-x ! to org-reload-uncompiled or another binding could be found. I don't think this is necessary, C-u C-c C-x ! is easy enough. BTW, I just see that the menu entry for loading org uncompiled is wrong, it still tries to run it via C-u C-c C-x r, which isn't bound anymore since Org 6.26d due to a conflict with bindings in other modes. Looks like nobody ever used this in the last four years… fixed in maint and merged to master. Thanks for fixing this! PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. -- Bastien
Re: [O] edit-src on read-only files
Hi Andreas, Andreas Leha andreas.l...@med.uni-goettingen.de writes: On a related note: I'd also love to see the changes in the source code buffers be autosaved in the org file. I've lost some big edits already due to power loss on my (old) laptop. There is now `org-edit-src-auto-save-idle-delay' which you can set to 0 so that the edit src buffer will be saved after N secs of idle time. Thanks for suggesting this, -- Bastien
Re: [O] {New exporter] What happened to the export template
Nicolas Goaziou n.goaz...@gmail.com writes: It has been removed. Such a template depends on the back-end used, which was not the case of the previous implementation. One idea would be to have an equivalent of the now-defunct `org-insert-export-options-template' but for each backend. For example `C-c C-e h t' would insert the default template for the HTML export. Is anyone interested in this? -- Bastien
Re: [O] Macro question with new texinfo exporter
Bastien writes: PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. These days I only ever use it for Show All which does have a menu entry, but no key binding. But before I got used to where the keys are I often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] {New exporter] What happened to the export template
Bastien b...@altern.org writes: Nicolas Goaziou n.goaz...@gmail.com writes: It has been removed. Such a template depends on the back-end used, which was not the case of the previous implementation. One idea would be to have an equivalent of the now-defunct `org-insert-export-options-template' but for each backend. For example `C-c C-e h t' would insert the default template for the HTML export. Is anyone interested in this? Well I found this template very helpful! I hope there will be an equivalent to it. I think (for the beginning) it could be a compilation of *all* back-end variations (commented out? I don't yet understand the new exporter concept). Thanks -- Best wishes H. Dieter Wilhelm Darmstadt Germany
Re: [O] LaTeX-export: letters after $..$ turn off math-mode
Completing myself, IMO, I would call that an Org limitation. Org is not LaTeX, even if it provides many LaTeX facilities. Also, the OP's problem can be solved in many ways under Emacs. For example, I use mt (both m and t are on my home row) as a snippet to insert \(\) in an Org buffer and put point inside. I would even go further. The following text has been in documentation for years: * Text within the usual LaTeX math delimiters. To avoid conflicts with currency specifications, single `$' characters are only recognized as math delimiters if the enclosed text contains at most two line breaks, is directly attached to the `$' characters with no whitespace in between, and if the closing `$' is followed by whitespace, punctuation or a dash. For the other delimiters, there is no such restriction, so when in doubt, use `\(...\)' as inline math delimiters. and so has been this excerpt from `org-inside-LaTeX-fragment-p' docstring: Even though the matchers for math are configurable, this function assumes that \\begin, \\(, \\[, and $$ are always used. Only the single dollar delimiters are skipped when they have been removed by customization. This function does a reasonably good job, but can locally be fooled by for example currency specifications. For example it will assume being in inline math after \$22.34\. The LaTeX fragment formatter will only format fragments that are properly closed, but during editing, we have to live with the uncertainty caused by missing closing delimiters. We cannot afford two maintain two implementations, one of them being frail, of the _same concept_. It's way better to focus on one of them, and make sure it is solid. It also means a slightly lighter Org, and less code to debug, which is always good. Thus, I suggest to announce that $ (both $ and $$, even though $$ don't have problems /per se/) symbols for should be avoided. Then, in a year or so, we can remove them completely from code base. Regards, -- Nicolas Goaziou
Re: [O] [TEXINFO] Link bug
t...@tsdye.com (Thomas S. Dye) writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
I think the new code to handle split links has broken links that aren't
split.
Here is an ECM:
* Headline to split
[[Headline
to split]]
[[Headline to split]], not!
This should be fixed. Could you confirm it?
Au contraire. Here's what I get with the ECM I sent earlier:
@node Headline to split
@chapter Headline to split
@ref{(Headline to split),}
@ref{(Headline to split),}, not!
Now, both the links are broken :(
This is good news: the problem is now consistent ;)
Anyway, these links export fine to LaTeX, HTML and ASCII, which means
the problem now resides in ox-texinfo.el.
I attach a suggested solution for the problem. Cc'ed Jonathan so he can
choose whether to apply it or not.
Regards,
--
Nicolas Goaziou
From 72985e92ab75c6b261bbec46aab2648098aac444 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou n.goaz...@gmail.com
Date: Sat, 16 Feb 2013 13:36:18 +0100
Subject: [PATCH] ox-texinfo: Fix fuzzy links to headlines
* lisp/ox-texinfo.el (org-texinfo--get-node): New function.
(org-texinfo-headline, org-texinfo-link): Use new function.
The same function is used to create @node entries and links to nodes,
to avoid any descrepency between them.
---
lisp/ox-texinfo.el | 29 ++---
1 file changed, 14 insertions(+), 15 deletions(-)
diff --git a/lisp/ox-texinfo.el b/lisp/ox-texinfo.el
index 20fa41d..3da567f 100644
--- a/lisp/ox-texinfo.el
+++ b/lisp/ox-texinfo.el
@@ -430,6 +430,17 @@ See `org-texinfo-text-markup-alist' for details.
;; Else use format string.
(t (format fmt text)
+(defun org-texinfo--get-node (headline info)
+ Return node entry associated to HEADLINE.
+INFO is a plist used as a communication channel.
+ (let ((menu-title (org-element-property :texinfo-menu-title headline)))
+(org-texinfo--sanitize-menu
+ (replace-regexp-in-string
+ % %%
+ (if menu-title (org-export-data menu-title info)
+ (org-texinfo--sanitize-headline
+ (org-element-property :title headline) info))
+
;;; Headline sanitizing
(defun org-texinfo--sanitize-headline (headline info)
@@ -896,22 +907,12 @@ holding contextual information.
(class-sectionning (assoc class org-texinfo-classes))
;; Find the index type, if any
(index (org-element-property :index headline))
- ;; Retrieve custom menu title (if any)
- (menu-title (org-texinfo--sanitize-menu
- (org-export-data
- (org-element-property :texinfo-menu-title headline)
- info)))
;; Retrieve headline text
(text (org-texinfo--sanitize-headline
(org-element-property :title headline) info))
;; Create node info, to insert it before section formatting.
;; Use custom menu title if present
- (node (format @node %s\n
- (org-texinfo--sanitize-menu
- (replace-regexp-in-string % %%
- (if (not (string= menu-title))
- menu-title
- text)
+ (node (format @node %s\n (org-texinfo--get-node headline info)))
;; Menus must be generated with first child, otherwise they
;; will not nest properly
(menu (let* ((first (org-export-first-sibling-p headline info))
@@ -1180,8 +1181,7 @@ INFO is a plist holding contextual information. See
;; LINK points to an headline. Use the headline as the NODE target
(headline
(format @ref{%s,%s}
- (or (org-element-property :texinfo-menu-title destination)
- (org-element-property :title destination))
+ (org-texinfo--get-node destination info)
(or desc )))
(otherwise
(let ((path (org-export-solidify-link-text path)))
@@ -1203,8 +1203,7 @@ INFO is a plist holding contextual information. See
;; LINK points to an headline. Use the headline as the NODE target
(headline
(format @ref{%s,%s}
- (or (org-element-property :texinfo-menu-title destination)
- (org-element-property :title destination))
+ (org-texinfo--get-node destination info)
(or desc )))
(otherwise
(let ((path (org-export-solidify-link-text path)))
--
1.8.1.3
Re: [O] [ox-publish] index file empty?
Hello, Stefan Vollmar voll...@nf.mpg.de writes: we are almost done migrating to the new exporter, currently the only showstopper is index generation, a feature we find very useful for our software documentation, here is an example generated with an older org version: http://www.nf.mpg.de/vinci3/doc/theindex.html ox-publish.el should create an index. Though, its caching mechanism isn't compatible with the old one. Could you try again after removing completely any cache from previous publish library? If it fails, would you mind providing an ECM? Thank you. Regards, -- Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Achim Gratz strom...@nexgo.de writes: Bastien writes: PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. These days I only ever use it for Show All which does have a menu entry, but no key binding. But before I got used to where the keys are I often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch
Re: [O] Follow link scrolls current buffer when table aligns
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: Minimal test to reproduce: 1) put the attached n.org and t.org into one directory 2) emacs -q 3) C-x 3 4) open n.org 5) M-, C-p, C-c C-o The last step changes the scroll state of n.org but the return value of window-start is expected be the same before and after. How can org-table-align be changed that set-window-start affects only the visited target buffer but not the original buffer which called find-file-noselect to follow its link? I finally fixed this with this commit: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=adcc0d Here is the git commit log: When opening an .org file from another .org file, org-mode is initialized in the second one while the window is not yet selected. So, functions run during org-mode's initialization need to check if the org-mode window is the selected one before manipulating the current window. Thanks for reporting this! -- Bastien
[O] `org-drill' broken in recent commits git commits
Hi there, `org-drill' has broken recently (after git commit 3380460), here is the steps to reproduce the issue: 1. Create a new org-mode buffer with the following contents: * org-drill test :drill: Foo ** Answer Bar 2. M-x org-drill 3. Press SPACE 4. Press `2' and you are stuck there forever until pressing `q' or C-g. Thanks, York
[O] Reloading uncompiled and testing from several git branches (was: Macro question with new texinfo exporter)
(Updating the subject.) Eric Abrahamsen e...@ericabrahamsen.net writes: Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch Yes, that's the mistake I often did. Especially because make test compiles the file and do not deleted the compiled files. Maybe we can have make testclean = make test make clean Achim, would that be useful? I don't compile and I reload with C-u M-x org-reload RET. This way I have no problem switching from one branch to another, provided my setup is not shadowing current variables the wrong way.) -- Bastien
Re: [O] [Bug] Yasnippet/Org: properties messed up when expanding $1
Karl Voit devn...@karl-voit.at writes: * Karl Voit devn...@karl-voit.at wrote: I updated Org to latest git and I moved from Debian yasnippet to github yasnippet (latest) and I still do have this issue. So it's my set-up which is causing this effect. Damn. I guess I have to debug this by disabling parts of my config ... So a quick test of my set-up with disabling all(!) of my Org-mode settings caused the same issue. Therefore, it's not my Org-mode set-up which is causing all this hazzle. Next test: «emacs -q» and I loaded only yasnippet: , | (defun my-load-local-el (part) ... ) | (my-load-local-el contrib/yasnippet/yasnippet.el) ;; load-path | (require 'yasnippet) | (setq yas/root-directory ~/.emacs.d/snippets) | (yas/load-directory yas/root-directory) ` And yes, I still got the issue. :-( I guess I have to do a bug report to yasnippet. I think I have the newest (github) yasnippet, and doing C-h f on yas/load-directory, it says that it is an obsolete function, recommending yas-load-directory instead. Maybe it is worth a try.
[O] [New exporter] Should there be an option to kill/exit the dispatcher without using it
System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is no simple option in the export dispatcher to either switch to and then kill or simply kill the export dispatcher UI (or buffer) if you do not want to use it after you call it. I called up the new dispatcher only for a look-see and no more. After C-c C-e, the point remained in the original buffer. I then wanted to kill/exit the dispatcher without using it. 1. I attempted to switch to the dispatcher. a. C-x exported the original buffer to XOXO. (no chance to enter the b key) b. M-x produced Wrong type argument: character, 134217848. There was no chance to enter switch buffer after M-x. 2. Just for fun I entered q and it produced No command associated with key q. In all three cases the dispatcher remained open but not visible. I was then able to switch to the dispatcher and kill it. Charlie Millar
Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it
My mistake. I forgot about C-g. Charlie On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is no simple option in the export dispatcher to either switch to and then kill or simply kill the export dispatcher UI (or buffer) if you do not want to use it after you call it. I called up the new dispatcher only for a look-see and no more. After C-c C-e, the point remained in the original buffer. I then wanted to kill/exit the dispatcher without using it. 1.I attempted to switch to the dispatcher. a. C-x exported the original buffer to XOXO. (no chance to enter the b key) b. M-x produced Wrong type argument: character, 134217848. There was no chance to enter switch buffer after M-x. 2.Just for fun I entered q and it produced No command associated with key q. In all three cases the dispatcher remained open but not visible. I was then able to switch to the dispatcher and kill it. Charlie Millar - No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2899 / Virus Database: 2639/6103 - Release Date: 02/14/13
Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it
I'm not sure if my immediate follow up was sent to the list. I forgot about C-g. Charlie Millar On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is no simple option in the export dispatcher to either switch to and then kill or simply kill the export dispatcher UI (or buffer) if you do not want to use it after you call it. I called up the new dispatcher only for a look-see and no more. After C-c C-e, the point remained in the original buffer. I then wanted to kill/exit the dispatcher without using it. 1.I attempted to switch to the dispatcher. a. C-x exported the original buffer to XOXO. (no chance to enter the b key) b. M-x produced Wrong type argument: character, 134217848. There was no chance to enter switch buffer after M-x. 2.Just for fun I entered q and it produced No command associated with key q. In all three cases the dispatcher remained open but not visible. I was then able to switch to the dispatcher and kill it. Charlie Millar - No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2899 / Virus Database: 2639/6103 - Release Date: 02/14/13
Re: [O] Reloading uncompiled and testing from several git branches
Bastien writes: Yes, that's the mistake I often did. Especially because make test compiles the file and do not deleted the compiled files. Maybe we can have make testclean = make test make clean Achim, would that be useful? We already have make test-dirty for testing without doing a compile. However, if you'd rather have that target, you can easily add it to local.mk: .PHONY: testclean # in case you'll ever have a file named testclean testclean: test clean In general all such targets that are simple combinations of existing teargets can be added that way. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it
Hello, Charles mill...@verizon.net writes: I'm not sure if my immediate follow up was sent to the list. I forgot about C-g. Charlie Millar On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is no simple option in the export dispatcher to either switch to and then kill or simply kill the export dispatcher UI (or buffer) if you do not want to use it after you call it. I called up the new dispatcher only for a look-see and no more. After C-c C-e, the point remained in the original buffer. I then wanted to kill/exit the dispatcher without using it. 1.I attempted to switch to the dispatcher. a. C-x exported the original buffer to XOXO. (no chance to enter the b key) b. M-x produced Wrong type argument: character, 134217848. There was no chance to enter switch buffer after M-x. 2.Just for fun I entered q and it produced No command associated with key q. In all three cases the dispatcher remained open but not visible. I was then able to switch to the dispatcher and kill it. If you see XOXO export, you're not looking at the new exporter interface. Regards, -- Nicolas Goaziou
Re: [O] Follow link scrolls current buffer when table aligns
Hi Bastien On Sat, Feb 16, 2013 at 2:13 PM, Bastien b...@altern.org wrote: I finally fixed this with this commit: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=adcc0d Fix confirmed. Thanks for reporting this! Thank you for the nice solution. Michael
Re: [O] Reloading uncompiled and testing from several git branches
Hi Achim, Achim Gratz strom...@nexgo.de writes: We already have make test-dirty for testing without doing a compile. However, if you'd rather have that target, you can easily add it to local.mk: .PHONY: testclean # in case you'll ever have a file named testclean testclean: test clean In general all such targets that are simple combinations of existing teargets can be added that way. Great, thanks for the tip! I'll use this. -- Bastien
Re: [O] LaTeX-export: letters after $..$ turn off math-mode
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: IMO, I would call that an Org limitation. I'm fine with the current limitation -- if that's just one email per year, I think we can handle this :) FWIW I'm not in favor of removing the ability to inline $x^2$ and to deprecate the use of $ completely. If this flexibility is not too problematic (from a maintainance point of view), I'd say it's fine to keep it. Thanks, -- Bastien
Re: [O] `org-drill' broken in recent commits git commits
Hi York, York Zhao gtdplatf...@gmail.com writes: Hi there, `org-drill' has broken recently (after git commit 3380460), here is the steps to reproduce the issue: 1. Create a new org-mode buffer with the following contents: * org-drill test :drill: Foo ** Answer Bar 2. M-x org-drill 3. Press SPACE 4. Press `2' and you are stuck there forever until pressing `q' or C-g. I cannot reproduce this. Does this happen with emacs -Q? What is your version of Emacs? Thanks, -- Bastien
Re: [O] new export dispatcher window
On Sat, Feb 16, 2013 at 2:09 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Use SPC, DEL, C-n or C-p to scroll. That works. Any reason scroll bars could not be enabled too? I see one, but any mouse clicks just generate spurious minibuffer messages. Thanks.
Re: [O] new export dispatcher window
Skip Collins skip.coll...@gmail.com writes: On Sat, Feb 16, 2013 at 2:09 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Use SPC, DEL, C-n or C-p to scroll. That works. Any reason scroll bars could not be enabled too? I see one, but any mouse clicks just generate spurious minibuffer messages. Thanks. When *Org Export Dispatch* is visible, the minibuffer will catch any event, including mouse clicks, until it recognizes a key. I think this limitation is not unbearable. Regards, -- Nicolas Goaziou
Re: [O] Reloading uncompiled and testing from several git branches
Achim Gratz strom...@nexgo.de writes: Bastien writes: Yes, that's the mistake I often did. Especially because make test compiles the file and do not deleted the compiled files. Maybe we can have make testclean = make test make clean Achim, would that be useful? We already have make test-dirty for testing without doing a compile. However, if you'd rather have that target, you can easily add it to local.mk: .PHONY: testclean # in case you'll ever have a file named testclean testclean: test clean Thanks for this pointer!
Re: [O] LaTeX-export: letters after $..$ turn off math-mode
Bastien b...@altern.org writes: FWIW I'm not in favor of removing the ability to inline $x^2$ and to deprecate the use of $ completely. If this flexibility is not too problematic (from a maintainance point of view), I'd say it's fine to keep it. While I agree that \(·\) is the preferred and Rightᵀᴹ delimiter pair I almost always use $·$ in place if I can get away with it. Thus, if the maintenance cost is low I would prefer if it stayed. Using the patch posted by Nicolas last week (i.e. (re)introducing org-highlight-latex-and-special) there's even visual feedback as to when Org will correctly identify $·$. /If/ a mechanism existed to easily use \(·\) I would be all for ditching $·$ as it clearly inferior (legacy documents can quickly be fixed via a regexp replacement, if needed). For instance, in ESS there is ess-smart-underscore where, depending on the context, pressing _ will usually do the right thing. For Instance $ could insert \(·\) or $ first (depending on the variable org-export-care-about-usd). On region it would always put it inside \(·\). But it might be messy, I'm not really sure. –Rasmus -- C is for Cookie
Re: [O] [Bug] Yasnippet/Org: properties messed up when expanding $1
* Rafael rvf0...@gmail.com wrote: I think I have the newest (github) yasnippet, and doing C-h f on yas/load-directory, it says that it is an obsolete function, recommending yas-load-directory instead. Maybe it is worth a try. Thanks for the hint but it does not change my behavior :-( As a matter of fact, while debugging the issue, I was using «YASnippet Reload everything» from the menu bar between each test. -- Karl Voit
Re: [O] Highlighting LaTeX fragments
Would you mind testing the following patch? I don't like it much because it's an all or nothing fontification. I think latex snippets, entities and sub/superscript should be separated. I have no experienced any problems. I agree that it would be better not to be able not to fontitfy rouge entities and super/subscripts. Anyway, does it replace the missing functionality? Yes, it seems so replicate the old behavior so far. –Rasmus -- A clever person solves a problem. A wise person avoids it
Re: [O] {New exporter] What happened to the export template
Bastien b...@altern.org writes: It has been removed. Such a template depends on the back-end used, which was not the case of the previous implementation. One idea would be to have an equivalent of the now-defunct `org-insert-export-options-template' but for each backend. For example `C-c C-e h t' would insert the default template for the HTML export. Is anyone interested in this? Not really. IMO, the old template added to much noise and didn't have nice defaults. That's purely subjective, though! IMO, it would be better to have a section on adopting mechanisms such as org-structure-template-alist for templates. Personally, I use org-latex-classes for rudimentary customizations (letter, problemset, thesis etc.). –Rasmus -- Send from my Emacs
Re: [O] Macro question with new texinfo exporter
Bastien b...@altern.org wrote: PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. I do: there are many things I use rarely[fn:1] (e.g. archiving, drawers, properties, even marking TODOs outside the agenda: was that C-c t or C-c C-t now?) that I have not got into my finger memory. The menu is a useful crutch for me in those cases: I use the menu the first time, put the key chord into short-term memory and forget about it as soon as I'm done. Two weeks later, I start from scratch :-) Nick Footnotes: [fn:1] An imprecise term, but for me that means less often than once a week. YMMV. And as one gets older, that mileage changes - DAMHIKT :-)
Re: [O] [TEXINFO] Link bug
Nicolas Goaziou n.goaz...@gmail.com writes: Now, both the links are broken :( This is good news: the problem is now consistent ;) Anyway, these links export fine to LaTeX, HTML and ASCII, which means the problem now resides in ox-texinfo.el. Thanks Nicolas. I'll wait for Jonathan to tweak ox-texinfo. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] LaTeX-export: letters after $..$ turn off math-mode
Nicolas Goaziou n.goaz...@gmail.com wrote: ... Thus, I suggest to announce that $ (both $ and $$, even though $$ don't have problems /per se/) symbols for should be avoided. Then, in a year or so, we can remove them completely from code base. Agree. Also $$ may not cause problems to org, but according to Lamport (see p. 233 of Lamport (2nd ed)) it does not work properly in LaTeX. Nick
Re: [O] Macro question with new texinfo exporter
Eric Abrahamsen e...@ericabrahamsen.net wrote: Achim Gratz strom...@nexgo.de writes: Bastien writes: PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. These days I only ever use it for Show All which does have a menu entry, but no key binding. But before I got used to where the keys are I often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch I don't trust org-reload enough for that: I write[fn:1] a minimal .emacs that does whatever it needs to do to get me to the problem as fast as possible and start a new emacs (emacs -q -l /path/to/minimal.emacs ...) Nick Footnotes: [fn:1] Write is a bit of an exaggeration: I have a standard one that I copy and modify for my current needs. When I'm done, I throw it away.
Re: [O] LaTeX-export: letters after $..$ turn off math-mode
Nick Dokos nicholas.do...@hp.com wrote: Nicolas Goaziou n.goaz...@gmail.com wrote: ... Thus, I suggest to announce that $ (both $ and $$, even though $$ don't have problems /per se/) symbols for should be avoided. Then, in a year or so, we can remove them completely from code base. Agree. Also $$...$$ may not cause problems to org, but according to Lamport (see p. 233 of Lamport (2nd ed)) it does not work properly in LaTeX. See also http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll for some details. Nick
Re: [O] Macro question with new texinfo exporter
Nick Dokos nicholas.do...@hp.com wrote: Eric Abrahamsen e...@ericabrahamsen.net wrote: Achim Gratz strom...@nexgo.de writes: Bastien writes: PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. These days I only ever use it for Show All which does have a menu entry, but no key binding. But before I got used to where the keys are I often used the menu to do things in tables, so I guess the menu gets good use by other new users of Org (just that apparently none of them tries to reload Org uncompiled). Related to this -- how do you folks handle multiple local git branches? Do you always run uncompiled, and follow every git checkout with org-reload? I've caught myself several times recently doing git checkouts and reloading, but of course still reloading the byte-compiled files from the previous branch I don't trust org-reload enough for that: I write[fn:1] a minimal .emacs that does whatever it needs to do to get me to the problem as fast as possible and start a new emacs (emacs -q -l /path/to/minimal.emacs ...) I do ``make clean'' early and often too...
Re: [O] {New exporter] What happened to the export template
Rasmus ras...@gmx.us writes: Not really. IMO, the old template added to much noise and didn't have nice defaults. That's purely subjective, though! That's what this thread is for -- collect purely subjective feedback so we can get a rough idea of whether it's useful to implement this feature or not :) -- Bastien
Re: [O] Macro question with new texinfo exporter
Nick Dokos nicholas.do...@hp.com writes: Bastien b...@altern.org wrote: PS: I wonder if *any* of the menu item is used... as I don't use the menu myself, it's hard to tell. I do: there are many things I use rarely[fn:1] (e.g. archiving, drawers, properties, even marking TODOs outside the agenda: was that C-c t or C-c C-t now?) that I have not got into my finger memory. The menu is a useful crutch for me in those cases: I use the menu the first time, put the key chord into short-term memory and forget about it as soon as I'm done. Two weeks later, I start from scratch :-) Nick Footnotes: [fn:1] An imprecise term, but for me that means less often than once a week. YMMV. And as one gets older, that mileage changes - DAMHIKT :-) My experience resembles Nick's. The menus save me lots of time. I'm not sure what DAMHIKT means, but there is no doubt that mileage changes with age. The term key chord puzzled me for a long time, until a colleague pointed out that it is possible to play a computer running Emacs, just like playing a piano. I was stunned! All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] exit code editing buffer without installing the changes
awesome. thanks! On Fri, Feb 15, 2013 at 3:00 PM, Bastien b...@altern.org wrote: Hi Zech, Not To Miss not.to.m...@gmail.com writes: I know in a source code block, C-c ' will launch a buffer to edit the source code and C-c ' again will install the buffer back to the code block. Sometimes I just want to abort all the changes, so I am wondering: Is there anyway to exit the buffer without installing the changes and return to the org file without any modification? I implemented this -- you can now use `C-c k' in the buffer, it will quit and restore the window config correctly. Thanks for suggesting this! -- Bastien
Re: [O] exit code editing buffer without installing the changes
Bastien b...@altern.org writes: Hi Zech, Not To Miss not.to.m...@gmail.com writes: I know in a source code block, C-c ' will launch a buffer to edit the source code and C-c ' again will install the buffer back to the code block. Sometimes I just want to abort all the changes, so I am wondering: Is there anyway to exit the buffer without installing the changes and return to the org file without any modification? I implemented this -- you can now use `C-c k' in the buffer, it will quit and restore the window config correctly. Thanks for suggesting this! We use C-c C-k to abort a capture buffer - would that key be more consistent? Regards, Bernt
Re: [O] [Feature Request] Cross headings in tables
I've just looked at how to implement this using org-element and the new exporter. Much to my dismay I found that table headers are not a separate row or row group type and the new exporter is still using this everything before the first separator is a heading kludge. It's easy enough to introduce a second type of separator in org-element (BTW, I don't think that 'rule is a particularly good symbol name for this) by adding another type of table rows, but then these lines get ignored by the new exporter. While the logic used there is amendable (not as easily), it would be more hackish than I hoped. Also, it appears that each element can have only one property or did I miss something? It seems that having a way to get the (main) property and then asking if there are sub-properties on that element would allow simpler code in this particular instance and likely elsewhere. Maybe I missed how to do it, though. The cleanest way to implement this would be if being a header would be a property of the row group (maybe returnable as the sign of the row group number). There'd be two types of separators, |- and |~. If the line past the end of a row group is |~, then it is a header group, otherwise it is a normal group. This is incompatible with tradition, but it would allow to use row groups in formulas without introducing unwanted headers. Thoughts? Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] block quotes in prose?
Bastien, thanks for the response and the explanation. Looks like getting
org-mode recognize the prefix as a demarcator of a code block isn't the
right approach then.
What about John Hendy's suggestion of finding a face I like, and then
adding ^ text... to the list of things org fontifies with that style?
('In other words, add ^ text regexp to the existing hunt for lines that
start with #+ in order to get src code fontification applied.')
Is this feasible? If so, how would I go about doing this? Sorry for the
newbie question. I'm looking in org-faces, and I don't see anywhere where I
can specify the prefix characters org looks for...
John Hendy wrote:
The easiet would be to find a face you like and just add ^
text... to the existing list of things org already fontifies with
that style. In other words, add ^ text regexp to the existing hunt
for lines that start with #+ in order to get src code fontification
applied.
On Mon, Feb 11, 2013 at 10:54 AM, Bastien b...@altern.org wrote:
Hi Peter,
Peter Salazar cycleofs...@gmail.com writes:
Now the question is: How do I make org-mode recognize the prefix
as a demarcator of a code block, so that my document remains readable
as Markdown?
You can't -- using : as the prefix for fixed-width regions is
hardcoded. If we allow to customize this, it will lower the
exchangeability of .org files between users (this exchangeability
is already quite low due to the many options user have.)
Best,
--
Bastien
Re: [O] exit code editing buffer without installing the changes
Bernt Hansen be...@norang.ca writes: We use C-c C-k to abort a capture buffer - would that key be more consistent? Indeed, I made this change, thanks! -- Bastien
Re: [O] Highlighting LaTeX fragments
Hello, Rasmus ras...@gmx.us writes: Would you mind testing the following patch? I don't like it much because it's an all or nothing fontification. I think latex snippets, entities and sub/superscript should be separated. I have no experienced any problems. I agree that it would be better not to be able not to fontitfy rouge entities and super/subscripts. Anyway, does it replace the missing functionality? Yes, it seems so replicate the old behavior so far. I have applied a small variant of the patch. You can configure `org-highlight-latex-and-related' variable to fontify said syntax separately. Regards, -- Nicolas Goaziou
Re: [O] Highlighting LaTeX fragments
Nicolas Goaziou n.goaz...@gmail.com writes: Would you mind testing the following patch? I don't like it much because it's an all or nothing fontification. I think latex snippets, entities and sub/superscript should be separated. I have no experienced any problems. I agree that it would be better not to be able not to fontitfy rouge entities and super/subscripts. Anyway, does it replace the missing functionality? Yes, it seems so replicate the old behavior so far. I have applied a small variant of the patch. You can configure `org-highlight-latex-and-related' variable to fontify said syntax separately. Thanks, I'll check it out. -- Got mashed potatoes. Ain't got no T-Bone. No T-Bone
Re: [O] new exporter fails to output footnotes?
On 2/13/13, Nicolas Goaziou n.goaz...@gmail.com wrote: Samuel Wales samolog...@gmail.com writes: They are missing from plain text export. Fixed too. Thank you. In HTML, how do you control the hlevel of the footnotes header? See `org-html-footnotes-section'. That looks good. Given that it includes things that might change in future versions of Org, do you think it might be good to separate out the hlevel so that users don't customize and then find that bugs are introduced because their customization is out of date? Also, there is a formatting issue with footnotes. Here they are in w3m: I cannot help you much at the moment, as I don't know well the HTML back-end and I'm not sure what a correct fix for this would be. Anyway, if you send the correct HTML that should be generated, I will fix it. No idea. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
[O] org-odt: command line options for soffice bug?
Hi, I was having issues exporting to a doc file with this in my init file: (setq org-export-odt-preferred-output-format doc) After some debugging, it appears my soffice command takes a single dash (-), not double dash (--) for command line arguments. When I change to soffice -headless -convert-to %f%x -outdir %d %i in org-odt.el, things seem to work. I am running org-mode 7.9.3e on Emacs 24.1.50.1 and LibreOffice 3.3.4 on Ubuntu 11.04. Not sure if this is specific to me or not, but it should be fixed in org-mode. Thanks! -- Vinh
[O] Problems with latex_class
Hi there, I just updated to the latest version of org. I have a couple of classes (ie latex packages and classes, etc) that I use frequently. These are defined using the add-to-list 'org-export-latex-classes function in my .emacs file For some reason the latest version of org doesn't recognize my classes. More specifically when I evoke the org-latex exporter I get an error message 'unknown latex class blah Does anybody know how to resolve this ? Thanks M
Re: [O] Reloading uncompiled and testing from several git branches
Achim Gratz strom...@nexgo.de writes: .PHONY: testclean # in case you'll ever have a file named testclean testclean: test clean In general all such targets that are simple combinations of existing teargets can be added that way. Allow me a pedantic nit-pick, yet nothing so important in practice nowadays. Any Makefile which lists dependencies while expecting them to be satisfied sequentially, one after another, is broken. Make does not (theoretically) guarantee the order, while in practice, all make programs I know satisfy dependencies from left to right. In theory, still, make and make -j4 (say) should yield the same actions and effect. Automake-generated Makefiles respect this — or at least, they once did, I did not check in a long while. François P.S. In fact, for the above reason and also for a flurry of other reasons, often related to portability, almost all Makefiles are broken. It is so difficult to get them right that an AM_MAINTAINER_MODE macro has been added to Automake as a way to generate and sanctify incorrect ones. A perfect Makefile is very rare.
[O] A proposal to integrate org-mode with bookmark+ (bookmark plus / bmkp) , org-bookmark and evince for bookmarking source code and pdf documents with exact coordinate
Hi there.
I'm very interested in the potential applications of org-mode, and spent some
time to write some code to facilitate the integration between bookmark+ and
evince.
I'd like to share the code with you and discuss with you about it.
There are primarily two use cases.
- To bookmark source code files (*.c *.h) with bookmark+
- essentially there's already org-bookmark.el in the contrib. accompanying
org-mode.
- when browsing codes, I bookmark with C-x r m , then enter the name, then a
bookmark is created for me
- then copy this bookmark with C-c l，then in the org file C-c C-l to insert
this bookmark link
- I made two changes here;
- when opening a bookmark link, I need to ensure that bookmark+'s
*Bookmark List* buffer is open in case it opens the vallina bookmark list
- really need the opened file shown in the other buffer
- the changes I made:
diff --git a/home/sig/src/org-mode/contrib/lisp/org-bookmark.el
b/home/sig/Dropbox/emacs/lisp/org-bookmark.el
index 5c669b0..170bd57 100644
--- a/home/sig/src/org-mode/contrib/lisp/org-bookmark.el
+++ b/home/sig/Dropbox/emacs/lisp/org-bookmark.el
@@ -52,7 +52,9 @@ Otherwise prompt the user for the right bookmark to use.
(defun org-bookmark-open (bookmark)
Visit the bookmark BOOKMARK.
- (bookmark-jump bookmark))
+ (unless (get-buffer *Bookmark List*)
+ (bookmark-bmenu-list))
+ (bookmark-jump-other-window bookmark))
(defun org-bookmark-store-link ()
Store a link to the current line's bookmark in bookmark list.
===
- To bookmark pdf files, which gets a little bit awkward...
- need to modify evince and create a global minor mode (in bmkp-evince.el
attached at the end of this mail) to handle the dbus communication
- pulled evince following https://live.gnome.org/Evince/GettingEvince
- I reused the syncview / syncsource calls, testing if auctex is present; if
not, then fall back into vallina mode in which
- when C-mouse click in evince, send a syncsource dbus message with
filename, page number and y coordinate
- the global minor mode picks up the syncsource message and add a
customized bookmark with customized handler
- then copy this bookmark with C-c l，then in the org file C-c C-l to insert
this bookmark
- when following the bookmark link in an org file, call the customized
handler,
- which in turn calls syncview, which opens the pdf file and scroll the
document to the place bookmarked
- know issues
- when the file is not already open, the call to syncview will open the
file; however the scrolling is broken somehow; any following call to syncview
works just fine; don't know why...
- I tried to make autoloads work in bmkp-evince.el but failed; don't know
why...
===
diff --git a/libview/ev-view.c b/libview/ev-view.c
index dd6b728..91bc096 100644
--- a/libview/ev-view.c
+++ b/libview/ev-view.c
@@ -3055,13 +3055,15 @@ ev_view_synctex_backward_search (EvView *view,
gint x_new = 0, y_new = 0;
EvSourceLink *link;
- if (!ev_document_has_synctex (view-document))
- return FALSE;
if (!get_doc_point_from_location (view, x, y, page, x_new, y_new))
return FALSE;
- link = ev_document_synctex_backward_search (view-document, page, x_new,
y_new);
+ if (ev_document_has_synctex (view-document))
+ link = ev_document_synctex_backward_search (view-document, page,
x_new, y_new);
+ else
+ link =
ev_source_link_new(g_path_get_basename(ev_document_get_uri(view-document)),
page+1, y_new);
+
if (link) {
g_signal_emit (view, signals[SIGNAL_SYNC_SOURCE], 0, link);
ev_source_link_free (link);
@@ -6023,7 +6025,16 @@ ev_view_highlight_forward_search (EvView *view,
GdkRectangle view_rect;
if (!ev_document_has_synctex (view-document))
- return;
+ {
+ page=link-line-1;
+ ev_document_model_set_page (view-model, page);
+ EvRectangle rect;
+ GdkRectangle view_rect;
+ view_rect.x=0; view_rect.y=0; view_rect.width=0;
view_rect.height=0;
+ rect.x1=0; rect.y1=link-col; rect.x2=0; rect.y2=link-col;
+ _ev_view_transform_doc_rect_to_view_rect (view, page, rect,
view_rect);
+ ensure_rectangle_is_visible (view, view_rect);
+ }else{
mapping = ev_document_synctex_forward_search (view-document, link);
if (!mapping)
@@ -6038,6 +6049,7 @@ ev_view_highlight_forward_search (EvView *view,
_ev_view_transform_doc_rect_to_view_rect (view, page, mapping-area,
view_rect);
ensure_rectangle_is_visible (view, view_rect);
+ }
gtk_widget_queue_draw (GTK_WIDGET (view));
}
diff --git a/shell/ev-window.c b/shell/ev-window.c
index 97f4a90..b6414a1 100644
--- a/shell/ev-window.c
+++ b/shell/ev-window.c
@@
Re: [O] Problems with latex_class
Marvin Doyley marvin...@gmail.com writes: Hi there, I just updated to the latest version of org. I have a couple of classes (ie latex packages and classes, etc) that I use frequently. These are defined using the add-to-list 'org-export-latex-classes function in my .emacs file We've got a new exporter now! It's really cool. For some reason the latest version of org doesn't recognize my classes. More specifically when I evoke the org-latex exporter I get an error message 'unknown latex class blah Does anybody know how to resolve this ? It's org-latex-classes now. Check out the announcement by Nicolas there will be some followups on the change of variable names. –Rasmus -- This is the kind of tedious nonsense up with which I will not put
Re: [O] Problems with latex_class
On Sat, Feb 16, 2013 at 06:51:02PM -0500, Marvin Doyley wrote: Hi there, I just updated to the latest version of org. I have a couple of classes (ie latex packages and classes, etc) that I use frequently. These are defined using the add-to-list 'org-export-latex-classes function in my .emacs file For some reason the latest version of org doesn't recognize my classes. More specifically when I evoke the org-latex exporter I get an error message 'unknown latex class blah Does anybody know how to resolve this ? The variable has been renamed to org-latex-classes for consistency. -- Suvayu Open source is the future. It sets us free.
Re: [O] org-agenda-show-log, org-timeline bugs
Bastien writes: Sorry, no special effort is made to fix bugs in org-timeline because its future is uncertain: there is significant overlap between this feature from the early days of Org, and the general agenda views mechanism. We'll make a decision about org-timeline before releasing Org 8.0: if it stays, let's fix it. If it goes, let's forget it! I found these bugs when I was using org-timeline to get an overview of work done during the past several months. The rest of the agenda code is forward-facing, so looking at historical data is one area where there is no overlap. Whether or not it needs to be part of the agenda framework is another matter. Derek -- Derek Upham s...@blarg.net
Re: [O] Problems with latex_class
On Sun, Feb 17, 2013 at 01:51:57AM +0100, Suvayu Ali wrote: On Sat, Feb 16, 2013 at 06:51:02PM -0500, Marvin Doyley wrote: Hi there, I just updated to the latest version of org. I have a couple of classes (ie latex packages and classes, etc) that I use frequently. These are defined using the add-to-list 'org-export-latex-classes function in my .emacs file For some reason the latest version of org doesn't recognize my classes. More specifically when I evoke the org-latex exporter I get an error message 'unknown latex class blah Does anybody know how to resolve this ? The variable has been renamed to org-latex-classes for consistency. Also check this out: http://orgmode.org/worg/org-faq.html#new-exporter-switch -- Suvayu Open source is the future. It sets us free.
Re: [O] Problems with latex_class
Thanks, I have made the changes and it is now working
Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it
Hello, Nicolas, On 2/16/2013 9:09 AM, Nicolas Goaziou wrote: Hello, Charles mill...@verizon.net writes: I'm not sure if my immediate follow up was sent to the list. I forgot about C-g. Charlie Millar On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is no simple option in the export dispatcher to either switch to and then kill or simply kill the export dispatcher UI (or buffer) if you do not want to use it after you call it. I called up the new dispatcher only for a look-see and no more. After C-c C-e, the point remained in the original buffer. I then wanted to kill/exit the dispatcher without using it. 1.I attempted to switch to the dispatcher. a. C-x exported the original buffer to XOXO. (no chance to enter the b key) b. M-x produced Wrong type argument: character, 134217848. There was no chance to enter switch buffer after M-x. 2.Just for fun I entered q and it produced No command associated with key q. In all three cases the dispatcher remained open but not visible. I was then able to switch to the dispatcher and kill it. If you see XOXO export, you're not looking at the new exporter interface. Regards, You are right. I was not looking at the new exporter. For that matter, I did not understand how to invoke the new exporter in a Windows 7 set up. That said, when I do load the new exporter as described in the release notes 7.9.2 on my system, the q key does not show on the dispatcher ui; however, pressing q does exit the dispatcher. On my Cygwin setup (same machine) the export dispatcher does show q as quit or exit. I update the org files in Cygwin using git, usually once per day. I looked at org/lisp and find that the exporter is now ox-[name]. Is that correct? Perhaps when the ox-[name] files become available in the org/lisp in Org 8 this option will appear in a plain Windows set up (if there is such a thing). I therefore conclude that someone has already suggested adding the line q for quit, that it has been implemented in the bleeding edge and I over looked any messages to that effect and my research was poorly executed. Best, Charlie
[O] org-weights.el
Hi, gang. A few times already, I spoke on this list of my need to see the weights of subtrees on header lines. Nicolas Goaziou was kind enough to write the function for computing the weights, I wrapped some Lisp code around this, and shared the result on this list. In that code, I had a command which computes and displays the weights, and as soon as I modify the buffer, the weights were disappearing. I recently had the need to frequently re-evaluate the weights after modifications, and got tired of repeating the displaying command after each modification. So I modified the code so the weights get updated instead of disappearing. Bastien also suggested that I turn my code into a small library. If you are curious, see the results as: https://github.com/pinard/org-weights It works relatively OK for me. Bugs surely remain. :-) François
[O] org-agenda-files skips two files
I've noticed for a while that two org files in my ~/org directory never get added to org-agenda-files, and I can't figure out why. My org-agenda-files is set to '(~/org/), and yet: (dolist (f (directory-files ~/org t org$)) (unless (member f org-agenda-files) (insert (format %s: %s\n f (file-attributes f) /home/eric/org/epubnotes.org: (nil 1 1000 100 (20752 42274) (20740 56906) (20740 56906) 10673 -rw-r--r-- nil 8655230 2052) /home/eric/org/running.org: (nil 1 1000 100 (20768 26205) (20768 21290) (20768 24128) 423435 -rw-r--r-- nil 5375520 2052) Those two files are never in there. I've tried to find at what point in the code org-agenda-files is first populated: obviously it happens after org-agenda is called for the first time, but I still can't find it! All variables related to filtering org agenda files are set to defaults. I can't see anything about the files themselves that would be objectionable. If I open them both manually, the second is added to the files list, but the first isn't! Very confused... Eric
Re: [O] Feature: Group and limit items in agenda
Yes I understand your point. However, setting TODO for each category manually would be laborious in my situation, I have to adjust the configuration file each time I add/delete the project. For my implementation, I advice on function 'org-agenda-finalize-entries' to put lists into different groups, limit them and add separator after the line '(setq list (mapcar 'org-agenda-highlight-todo list))' There's a 'org-agenda-before-sorting-filter-function' variable. However, I'm not able to use it for grouping things, because it's used as '(mapcar org-agenda-before-sorting-filter-function list)' Would it be useful to add another function here, not used in 'mapcar', but work directly on the whole list? I don't know whether it is worthy, and I'm OK if that's not general enough to be added, because I can use defadvice anyway :) On Mon, Feb 11, 2013 at 9:42 PM, Bastien b...@altern.org wrote: Hi Muchenxuan, Muchenxuan Tong demon...@gmail.com writes: My intention is to limit the number of tasks in each category. Did you check (info (org)Block Agenda) ? That's the way I would suggest: define a block agenda listing the various categories, then use `org-agenda-max-todos' in each of them to limit the number of TODOs. For the new proposed 'org-agenda-max-todos', I can only limit the number of TODOs in the whole TODO lists. Maybe for what I want, it's desirable to add a auto-split or auto-group features, where a list of TODOs, can be split further into multiple lists of TODOs, by a certain criteria (tags, category). What do you think about it? I understand defining block agendas is not as straightforward than the solution you envision, but my feeling is that allowing grouping+limits will have too much overlap with the block agenda functionality. Let me know if you find the path to happiness with a combinaison of block agendas and the new variables. Thanks, -- Bastien
