[O] Autocomplete for header arguments submitted?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi has the patch for the autocomplete of the header arguments been submitted to git? If yes, I have a problem on my side... Cheers, Rainer - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+RJAQACgkQoYgNqgF2egq0YgCffUjEN1hQKzYU7p1gM7f5cNMd ybIAn0B+tPVxLgCl5d57GoiezoX/hf8X =g8FO -END PGP SIGNATURE-
Re: [O] Drawers within inline tasks
Hi, when I open the parent task of an inline task drawers are not folded anymore. Not sure when this regression occured. Cheers, Viktor Bastien wrote: Hi Viktor, Viktor Rosenfeld listuse...@googlemail.com writes: Thanks for the quick patch, but there's a small problem. The drawer is collapsed if the inline task is opened, but not if the parent task is opened. Example: * Parent Task *** Inline Task :PROPERTIES: :Effort: 0:15 :END: *** END Pressing TAB on Inline Task keeps the property drawer collapsed. Pressing TAB on Parent Task opens it. Fixed, thanks. I first didn't take care of this because it seemed logical to show all the content of an inline task here: the purpose of the inline task is to stay out of the hierarchical structure, such a task is *not* a subtree... so the real content of Parent task is all the text below -- whether it contains inline tasks or not. But I can see that it's not visually consistent with the habit of keeping stuff folded, so let's go that way. Thanks for reporting this, -- Bastien
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
Hello, Shaun Johnson sh...@slugfest.demon.co.uk writes: Shaun Johnsonsh...@slugfest.demon.co.uk writes: The attached example org file (t.org) with two footnotes generates the attached HTML file (t.html). As you can see in the attached screenshot (t.png) the footnote placement is odd to say the least. This is a limitation from HTML exporter: it requires `org-footnote-section' being non-nil. Ah, ok, thanks. Is this documented? No. I have pushed a workaround in master. Can you confirm that HTML exporter now behaves as expected? Regards, -- Nicolas Goaziou
Re: [O] HTML slides
On Thu, Apr 19, 2012 at 3:38 PM, Dov Grobgeld dov.grobg...@gmail.com wrote: There is also https://github.com/dov/org-slidy , which I wrote since I like to be able to scroll my slides which S5 does not allow. It would be even cooler to create a package for creating HTML5 slideshows straight from org-mode, e.g. like http://slides.html5rocks.com/#table-of-contents or Which already exists: https://gist.github.com/509761 -Ista http://imakewebthings.com/deck.js . Regards, Dov On Thu, Apr 19, 2012 at 10:13, BernardH gmane.emacs.orgm...@bernard-hugueney.org wrote: Hi, First and foremost, thank you for making such a great emacs mode ! Whatever I'm doing with orgmode (and I do as much as possible in orgmode !), it is always a joy. Recently, i've been switching to orgmode for my presentations. I'm a happy user of [[https://github.com/eschulte/org-S5][org-S5]] but I just stumbled upon [[https://github.com/relevance/org-html-slideshow][org-html-slideshow]]. I have the utmost respect for their respective authors (of org-S5 for obvious reasons, of org-html-slideshow for Clojure contributions) and now I have a hard time deciding which one to choose. Does anyone have experience with any / both of them ? How would you make the choice ? Thanks for any advice ! Best Regards, Bernard
Re: [O] [PATCH] org-latex.el: append final newline to export buffer
jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes: org-export-as-latex (sometimes?) doesn't add a final newline to the exported buffer. It's getting in my way as I set require-final-newline to 'query. Opinions? Accepted and applied in master. Thanks. -- Bastien
Re: [O] org-protocol-capture and chrome
Bernt Hansen be...@norang.ca writes: Harri Kiiskinen harki...@gmail.com writes: The format of the patch was probably not correct as I have no idea whether it made it anywhere from this list, but should be found in the archives around April 14th. It's sitting on the patchwork server waiting to be dealt with. http://patchwork.newartisans.com/project/org-mode/list/ -Bernt Would be nice : seems straightforward enough and totally backwards comaptible. Nice one Harri. Chrome is pretty much #1 browser these days and building user base all the time.
Re: [O] org-protocol-capture and chrome
Richard Riley rile...@gmail.com writes: Bernt Hansen be...@norang.ca writes: Harri Kiiskinen harki...@gmail.com writes: The format of the patch was probably not correct as I have no idea whether it made it anywhere from this list, but should be found in the archives around April 14th. It's sitting on the patchwork server waiting to be dealt with. http://patchwork.newartisans.com/project/org-mode/list/ -Bernt Would be nice : seems straightforward enough and totally backwards comaptible. Nice one Harri. This has just been applied. Thanks, -- Bastien
Re: [O] Autocomplete for header arguments submitted?
Hi Rainer, Rainer M Krug r.m.k...@gmail.com writes: has the patch for the autocomplete of the header arguments been submitted to git? If you're talking about this patch http://patchwork.newartisans.com/patch/1281/ yes, it has been applied against master. I just marked it archived, in case that was why you asked. -- Bastien
Re: [O] Drawers within inline tasks
Hi Viktor, Viktor Rosenfeld listuse...@googlemail.com writes: when I open the parent task of an inline task drawers are not folded anymore. Not sure when this regression occured. Allowing tihs was causing performance regression in `org-cycle-internal-local'. If you can provide a patch that let `org-cycle-internal-local' without any performance regression, please do. Thanks, -- Bastien
Re: [O] [PATCH] Separate file time from its tasks times
Hi Sébastien, I introduced `org-clock-file-time-cell-format' which does the same thing than `org-clock-total-time-cell-format' for the file time. The original display of the clock table with the default values for both options is consistent. Putting the File time in a different column would require putting the Total time in yet another column, which IMO makes the clock table to large. Best, -- Bastien
Re: [O] [PATCH 1/2] Simplify org-clocktable-indent-string.
Hi Nicolas, Nicolas Girard girard.nico...@gmail.com writes: --- lisp/org-clock.el |6 +- 1 files changed, 1 insertions(+), 5 deletions(-) diff --git a/lisp/org-clock.el b/lisp/org-clock.el index 591f59c..be66ce6 100644 --- a/lisp/org-clock.el +++ b/lisp/org-clock.el @@ -2342,11 +2342,7 @@ from the dynamic block definition. (defun org-clocktable-indent-string (level) (if (= level 1) -(let ((str \\__)) - (while ( level 2) - (setq level (1- level) - str (concat str ___))) - (concat str +(concat \\ (make-string (* 2 (1- level)) ?_ ) ))) (defun org-clocktable-steps (params) Step through the range to make a number of clock tables. The simplification does not produce the same output. I rejected this patch. -- Bastien
Re: [O] [PATCH 2/2] Allow org-collector to display heading indentation by passing ':indent t' to the propview block.
Hi Nicolas, the patch does not apply against master and does not have a changelog entry. Please resubmit it with a Changelog entry and check that it applies against master correctly. Thanks, -- Bastien
Re: [O] [PATCH] Time specifications: Allow specifying relative times
Hi Ilya, Ilya Shlyakhter ilya_...@alum.mit.edu writes: When specifying times in the tags/properties matcher you can use relative time notation, such as yesterday or -1w. This patch allows this to be used in other places, such as the :tstart and :tend parameters of clocktable. Applied, thanks! -- Bastien
Re: [O] [bug] Remote durations are considered as fractions
Hi Sébastien, Sebastien Vauban wxhgmqzgw...@spammotel.com writes: BTW, *could we limit the format of T to H:MM*, instead of H:MM:SS? The first case seems much more common, and the one used in all time clocking functions of Org. Patch welcome! -- Bastien
Re: [O] org-program-exists vs executable-find
Hi Sébastien, Sebastien Vauban wxhgmqzgw...@spammotel.com writes: The name `org-program-exists' is actually misleading, it should be `org-executable-call' instead, while still checking if the executable exists before calling it. Nope, the name is not misleading. The documentation string is false -- what I hadn't noticed, btw. That function just checks if the executable can be found; it does _not_ call it afterward. You're right, I just fixed the docstring. On Linux and Mac OS, it just calls which + program name, no more... On Windows, it simply fails immediately (even if the program could be found). If there is an equivalent of `which' on windows let me know, we can generalize this function. Thanks, -- Bastien
Re: [O] More than one column view in a file
Hi Sébastien, Sebastien Vauban wxhgmqzgw...@spammotel.com writes: I'd like to have a couple of different (column) views in my Org file This is currently not possible and would require a lot of work. Best, -- Bastien
[O] org-clocktable: Show timestamps for CLOCKED
Hello, I'm currently running a report on my tasks last month. It works pretty fine using the following clocktable invocation: #+BEGIN: clocktable :maxlevel 2 :scope subtree :compact t :timestamp t #+END: This gives me a nice exportable clocktable for the current subtree (which is what I've done for work last month). However, one thing isn't very nice. One (big) task was clocked over two consecutive days: CLOCK: [2012-03-30 Fri 12:45]--[2012-03-30 Fri 18:25] = 5:40 CLOCK: [2012-03-29 Thu 14:45]--[2012-03-29 Thu 19:11] = 4:26 org-clocktable's :timestamp doesn't handle this, showing the task only with one timestamp in the table. This is as expected as the doc says: Look for SCHEDULED, DEADLINE, TIMESTAMP and TIMESTAMP_IA, in this order.. I think org-clocktable should search for CLOCKED too. -- Moritz Ulrich
Re: [O] [PATCH] Add autoload cookie for function org-table-iterate-buffer-tables
Hi Sébastien, Sebastien Vauban wxhgmqzgw...@spammotel.com writes: In the same vein, I found `org-update-all-dblocks', for which I propose a patch hereafter. Applied against master, thanks. I've scanned the 121 occurrences of `(interactive)' in `org.el' to look for extra potential candidates to the autoloading, but did not find any useful ones. Hence, just this one to add: Thanks for the thorough check! From 3df73c03d9a8c56189cbe91ec752bcc3269536ca Mon Sep 17 00:00:00 2001 From: Sebastien Vauban s...@mygooglest.com Date: Wed, 18 Apr 2012 11:12:00 +0200 Subject: [PATCH 3/3] Add autoload cookie for org-update-all-dblocks 2012-04-18 Sebastien Vauban wxhgmqzgw...@spammotel.com ^^ You don't need to add the line above in your ChangeLog entry. * org.el (org-update-all-dblocks): Autoload function. Thanks, -- Bastien
Re: [O] org-protocol-capture and chrome
Bastien b...@altern.org writes:
Richard Riley rile...@gmail.com writes:
Bernt Hansen be...@norang.ca writes:
Harri Kiiskinen harki...@gmail.com writes:
The format of the patch was probably not correct as I have no idea
whether it made it anywhere from this list, but should be found in the
archives around April 14th.
It's sitting on the patchwork server waiting to be dealt with.
http://patchwork.newartisans.com/project/org-mode/list/
-Bernt
Would be nice : seems straightforward enough and totally backwards
comaptible. Nice one Harri.
This has just been applied. Thanks,
Seems better but using this bookmark:-
,
| javascript:location.href='org-protocol://capture://'+ location.href+'/'+
document.title+'/'+ window.getSelection()
`
and this capture template:-
,
| (z default entry (file+datetree journal.org)
| * %^{Title}\n\t:PROPERTIES:\n\t:DateCreated:
%T\n\t:END:\n Source: %u, %c\n\n %i
| :empty-lines 1)
`
with org-protocol-default-template-key set to z the resulting popup
capture buffer still has the incorrect format for the url link. When I
C-c C-l on the Source link (%c which is the kill ring head ) I get only
http: in the Link: field and pressing enter on it doesnt do the
xpexted thing (open the link). I dont know which side this needs to be
fixed : possibly %c needs to be reparsed and constructed as a legitimate
org link element?
Re: [O] Use id property as anchor in the Table of Contents
Hi Olaf, Olaf Dietsche olaf+list.orgm...@olafdietsche.de writes: You might try this *untested* patch. It is against git master. Thanks a lot for this patch. I won't apply tho, because it might break the current setup of users who use :ID: and expect sec- to be the prefix for the anchor. We will try to handle Pere's request when integrating the new HTML exporter. Best, -- Bastien
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
On 20/04/2012 10:21, Nicolas Goaziou wrote: Hello, Shaun Johnsonsh...@slugfest.demon.co.uk writes: Shaun Johnsonsh...@slugfest.demon.co.uk writes: The attached example org file (t.org) with two footnotes generates the attached HTML file (t.html). As you can see in the attached screenshot (t.png) the footnote placement is odd to say the least. This is a limitation from HTML exporter: it requires `org-footnote-section' being non-nil. Ah, ok, thanks. Is this documented? No. I have pushed a workaround in master. Can you confirm that HTML exporter now behaves as expected? Yes, it now behaves as expected on my real document. Many thanks, Shaun.
Re: [O] [Feature Request] org-mobile edit:add nodes
Hi Henning, I'm not using org-mobile.el so it's hard to test this patch. Can anyone test and report? Henning Weiss hdwe...@gmail.com writes: I am currently trying to allow mobileorg-android to capture new headings into files other than mobileorg.org. It seems to me that org-mobile does not support refiling of nodes. As my experience with lisp programming is very limited, I was hoping someone on this list could add this feature. -- Bastien
Re: [O] bug#11249: 24.1.50; Overlay with face property causes calendar buffer to scroll
Toby Cubitt ts...@cantab.net writes: On Mon, Apr 16, 2012 at 05:50:50AM +0300, Eli Zaretskii wrote: Date: Sun, 15 Apr 2012 23:04:16 +0200 Cc: 11...@debbugs.gnu.org, emacs-orgmode@gnu.org From: Toby Cubitt toby-dated-1335733484.f89...@dr-qubit.org The obvious solution is for org-mode to use a face that doesn't enlarge the characters. Another solution would be to enlarge the calendar window by one line. I've attached a patch that does exactly this. As expected, it fixes the bug for me. As discussed previously, the alternative solution would be to change the default face used to highlight the current date to something that doesn't set the :bold attribute (which would probably mean introducing a separate face for this, instead of reusing org-warning). But expanding the calendar window is a more general solution, as it fixes the problem for (almost) any face. I introduced a new face `org-date-selected' which is now the one in use in the calendar and which is not bold. Thanks for the detailed feedback, -- Bastien
Re: [O] [PATCH] Allow more control over inserted whitespace in capture templates
Hi Toby, Toby Cubitt ts...@cantab.net writes: When capturing an item as a subheading, the capture template :empty-lines property is not sufficient to ensure the correct document layout is maintained after capturing. This patch fixes the capture behaviour to insert new subheadings immediately after the previous heading (rather than immediately before the next one). And it adds new :empty-lines-before and :empty-lines-after capture template properties. (I can split these two changes into separated patches, if desired.) Applied in master, thanks. -- Bastien
Re: [O] [PATCH] Add new '[not]todo-unblocked tests to org-agenda-skip-if
Toby Cubitt ts...@cantab.net writes: This patch adds two new tests to `org-agenda-skip-if': 'todo-unblocked and 'nottodo-unblocked. These match like 'todo and 'nottodo, but only on unblocked todo items. This type of test is useful when compiling custom agenda views containing lists of currently actionable todo items. Applied, thanks! -- Bastien
Re: [O] Various org-mode patches
Hi Toby, Toby Cubitt ts...@cantab.net writes: I finally found time to gather various local patches to org-mode together in a public clone of the org-mode git repo, at: http://www.dr-qubit.org/git/org-mode.git If there are patches that still need to be applied from this branch, can you send them one by one on the list? Thanks! -- Bastien
Re: [O] Fast linking to files in private git repos through a hyperlink
Hi Dov, Dov Grobgeld dov.grobg...@gmail.com writes: I thought I would share the following hack that I did with git. In my org-mode notebook I often find myself references files that reside in various private git repos. So far I have referenced these either by just writing their name or giving a full path. But giving the full path is disruptive and if the repo moves it will no longer work. So I added a hack to make the following hyperlink work git:myrepo::myfile . When opening it the following happens: - myrepo is looked up in the emacs hash my-git-repos and mapped to the path of a git repo root. - git-find-file-in-repo searches for the the file myfile in the the repo repo Here's the code for org-git-hyperlink.el: Nice. Can you try to merge these features with contrib/lisp/org-git-link.el from the current repo? Thanks! -- Bastien
Re: [O] HTML slides
Hi Ista, Ista Zahn istaz...@gmail.com writes: On Thu, Apr 19, 2012 at 3:38 PM, Dov Grobgeld dov.grobg...@gmail.com wrote: There is also https://github.com/dov/org-slidy , which I wrote since I like to be able to scroll my slides which S5 does not allow. It would be even cooler to create a package for creating HTML5 slideshows straight from org-mode, e.g. like http://slides.html5rocks.com/#table-of-contents or Which already exists: https://gist.github.com/509761 Nice. I added a section in worg/org-contrib/index.org to mention these possibilities. Does anyone can contact Kinjo (author of the above file) and let him know that the credit/author is wrong on his file? Thanks, -- Bastien
Re: [O] Various org-mode patches
On Fri, Apr 20, 2012 at 01:59:42PM +0200, Bastien wrote: Hi Toby, Toby Cubitt ts...@cantab.net writes: I finally found time to gather various local patches to org-mode together in a public clone of the org-mode git repo, at: http://www.dr-qubit.org/git/org-mode.git If there are patches that still need to be applied from this branch, can you send them one by one on the list? Sure, no problem. As you've no doubt seen, I already sent some of them separately. But I didn't want to bombard you with too many all at once ;-) So I paused on sending out the others. I'll post the others one by one when I find a spare moment. Cheers, Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org
Re: [O] agenda appt warn time (baby step part 2)
Hi Ivan, Ivan Kanis ivan.ka...@googlemail.com writes: The previous patch I sent was completely buggy. This one works but doesn't fulfill my RFC. I think the warn time should be somewhere within the time stamp... Inserting warntime in the headline looks hackish. Maybe have a look at contrib/lisp/org-notify.el by Peter? It does this and much more. Best, -- Bastien
Re: [O] [PATCH] Separate file time from its tasks times
Hi Bastien, I'd like to give my opinion on this subject. The original display of the clock table with the default values for both options is consistent. Putting the File time in a different column would require putting the Total time in yet another column, which IMO makes the clock table to large. First of all, I agree with you on the fact that the current way of presenting the table is clear enough, at least if you keep bold formatting for file times. If I understand well, Sebastien's problem is due to the fact that he has to remove the bold formatting in order to be able to make references to this table's cells (in order to use its content value in a formula). Removing bold formatting makes things unclear as you end up with 3 levels on the same column (grand total, file totals and first level heading totals). In this case, I agree with Sebastien and I would prefer to split the first column into 2, keeping the grand total and file totals on the first column. So, in my opinion, I see 2 solutions (which are not exclusive): 1) Be able to use a cell's content value in a formula even if a special formatting is used in that cell; if there's already a way to achieve this today, please tell us... 2) Follow Sebastien's idea in order for one to choose how to display the first 3 levels (grand total, file times and first level heading totals): in either 1 or 2 or 3 columns. The default being 1 column, corresponding to the current behavior. Hope this helps. Thanks, Francesco
Re: [O] Yearly repeats on the agenda
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: so it becomes 2012-04-17.*?. Hence it removes the date in the third example above, but not in the other two. The question is whether this is intended or not I think this is intended. If timestamps were not removed from today's date, agenda listing items scheduled/timestamped for today would be less readable. -- Bastien
Re: [O] Usage of disqus instead of mailinglist considered harmful
Hi Kyle, Kyle Sexton k...@mocker.org writes: Some other options could be: - Roll our own commenting system (a quick github search found https://github.com/phusion/juvia) - Setup automatic backups of comments using the disqus API, http://docs.disqus.com/developers/export/ Thanks for the link. I can search around and setup a commenting engine server and try to integrate it into worg like disqus, but unless it's an official server it's not much better. If random server someone sets up suddenly disappears it's the same as disqus changing their business model. I guess maybe a server with automatic comment exporting to git or something? Or org-maintainer admin access to server? Both? Maybe first setup an instance on your server so that we can test it. Then if people prefer this solution and Jason is okay to work with you on installing it on orgmode.org, let's do this. Thanks! -- Bastien
Re: [O] [PATCH] Agenda: Fix org-agenda-bulk-toggle when point is at already marked item
Hi Madan, Madan Ramakrishnan madan...@gmail.com writes: * lisp/org-agenda.el (org-agenda-bulk-mark): truly make arg optional as advertised by the function applied, thanks. This is my first patch for org so apologies for any inadvertent missteps This is good, but please use plain text emails if possible. Nick Dokos nicholas.do...@hp.com writes: I presume arg can be negative or zero. A value of arg below 1 doesn't make sense: arg drives the number of entries that will be marked, so users usually use this for arg 1. If (arg 1) then the function should trigger an error, which it does. Best, -- Bastien
Re: [O] food for thought re. git workflows
Nick Dokos nicholas.do...@hp.com writes: I thought this was an interesting read: http://sandofsky.com/blog/git-workflow.html *Very* interesting. Thanks Nick! -- Bastien
Re: [O] new style of html export for documents with code blocks -- based on docco
Hi Eric, Eric Schulte eric.schu...@gmx.com writes: This is a simple little hack, and I don't really have time to turn it into anything more than that, but the following may be used to generate nice side-by-side docco-style exports of Org-mode documents with code blocks. http://eschulte.me/org-docco/org-docco.html Can you please add this somewhere on Worg? Thanks! -- Bastien
Re: [O] Capturing to current file
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: Charles mill...@verizon.net wrote: I thought that the manual states to capture a TODO to the current file use /C-0 (zero) then proceed with the capture. I use this frequently. Am I missing something in the question? Probably not - I just didn't know about this method. It's not quite a capture (no indirect buffer, no finalize) but that hardly matters. And perhaps it also does what Samuel Wales asked about, since the template can be inserted anywhere at all. BTW, I only found this with C-h f org-capture, not in the manual. If there is a place in the manual that it should be documented, can you please point at this place and suggest a change? Thanks, -- Bastien
Re: [O] Yearly repeats on the agenda
Bastien bzg at altern.org writes: I think this is intended. If timestamps were not removed from today's date, agenda listing items scheduled/timestamped for today would be less readable. If the year in the timestamp of +1y repeating items is the current year, it *is* removed from the agenda. However, if the year is not the current year, then the timestamp is *not* removed from the agenda.
Re: [O] Combining font commands
Hi Yurb, YurB yurk...@gmail.com writes: Is there any way to have both bold and italic font on the same word like */this/* somehow? No, sorry. -- Bastien
Re: [O] bug with org-mode-hook and text-scale-set
Hi Matt, Matt Lundin m...@imapmail.org writes: Matt Lundin m...@imapmail.org writes: Bastien b...@gnu.org writes: Du Yanning duyann...@gmail.com writes: text-mode-hook and c-mode-hook do NOT have this bug. and the org-mode-hook of orgmode shipped within emacs 23.3 does NOT have this bug. This is now fixed, thanks. The problem was that Org relied on `face-remapping-alist' to remap the 'default face to the 'org-default face. Relying on this mechanism produces the error you reported, because the text-scale-set doesn't interact well with remapped faces. I'm now relying on `buffer-face-mode' which seems to be a cleaner approach. On my machine, this change causes a noticeable lag when typing in org-mode buffers. The cursor hesitates for a bit and then lurches forward. If I turn off buffer-face-mode the lag disappears. I'm still figuring out how to diagnose the problem. Another question: is it customary for major modes to invoke buffer-face-mode? Emacs devs said using buffer-face-mode is obnoxious. So I buffer-face-mode is not turned on by default anymore. org-default is still the face for buffer-face-mode, though. -- Bastien
Re: [O] Various org-mode patches
Toby Cubitt ts...@cantab.net writes: I'll post the others one by one when I find a spare moment. Thanks in advance! -- Bastien
Re: [O] a turn-key org-mode for newbies?
Eric Schulte eric.schu...@gmx.com writes: Although, a simpler system based off a single Org-mode file may be preferable. Agreed. I long dreamed of an Org tutorial written with elisp source blocks, demonstrating the use of various options incrementally? Any taker? -- Bastien
Re: [O] Bug in org-diary (Bad sexp)?
Hi Rafael, Rafael rvf0...@gmail.com writes: FWIW, using the tip from http://lists.gnu.org/archive/html/emacs-orgmode/2012-04/msg00702.html to go back to a previous state, I can confirm that commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 is good and that commit 973efcd9c9f5a29ffc9db2c317fab44112a97b07 introduced the error described above. I noticed the same problem, coming from the sticky-agenda merge. Max, Carsten, can one of you look into this? -- Bastien
Re: [O] Yearly repeats on the agenda
Bastien b...@altern.org wrote: Hi Nick, Nick Dokos nicholas.do...@hp.com writes: so it becomes 2012-04-17.*?. Hence it removes the date in the third example above, but not in the other two. The question is whether this is intended or not I think this is intended. If timestamps were not removed from today's date, agenda listing items scheduled/timestamped for today would be less readable. Oh, I agree - the removal is certainly desirable. I meant whether the non-removal of not-today's date is intentional :-) Nick
Re: [O] Brackets around title in HTML from org-e-html
Hi Shaun, Shaun Johnson sh...@slugfest.demon.co.uk writes: The appended org file when exported to HTML using org-e-html (via org-export-dispatch) has brackets around the title. The generated HTML is attached (t.html) as is a screenshot (t.png). How can I avoid these brackets being inserted? Mhh.. I cannot reproduce this. Anyone else? -- Bastien
Re: [O] [PATCH] doc/org.texi: Fix typos of function names in Agenda commands
Ippei FURUHASHI top.tuna+orgm...@gmail.com writes: Hi org-mode maintainer, There seems to be 2 discrepancies between a function name and its keybinding, in doc/org.texi. Could you have a look the following patch please? Applied, thanks! -- Bastien
Re: [O] [PATCH] Make [fragile] work with overlay specifications.
Hi Christoph, Christoph Dittmann git...@christoph-d.de writes: I noticed something unexpected in org-beamer.el when I used overlay specifications together with optional parameters for the frame environment and the frame contained verbatim sections. In this case the exporter would add [fragile] to the frame options in a way that would break the LaTeX code. I wrote a small patch that fixes this particular problem for me. Applied, thanks. -- Bastien
Re: [O] Usage of disqus instead of mailinglist considered harmful
Bastien b...@altern.org writes: Maybe first setup an instance on your server so that we can test it. Then if people prefer this solution and Jason is okay to work with you on installing it on orgmode.org, let's do this. Ok, I'll setup an instance to let people play with and see if it's a worthwhile endeavor. We can go from there if people actually use/like it. :) -- Kyle Sexton
Re: [O] Flexible plain list bullets
Hi Mark, I agree with Nicolas that a solution based on overlays would be better. I also agree with you that there are many areas where we let the users modify the content of Org files in a way that makes them unparsable in a systematic manner. This is always a trade-off: user flexibility vs a rigid syntax. On top of this trade-off there are many other one to consider, based on what are the available human (benevolent) resources to maintain Org. I try to prioritize things this way: 1. fix current bugs 2. improve syntax stability (against current state of flexibility) 3. extend current features 4. integrate new features Sometimes, a request raises a discussion somewhere between (3) and (2) -- which is precisely the discussion we have now. But pointing at failure in the current syntactic ground does not help promoting a feature request at (3) :) Also, Nicolas is working on a generic parser which will be the base for future decision on (2), and (consequently) on (3). So yes, this is complicate. We have many users. And an overlay based solution will *not* be a temporary fix, it will be something that any user can enjoy. Thanks, -- Bastien
Re: [O] Brackets around title in HTML from org-e-html
On 20/04/2012 14:19, Bastien wrote: Hi Shaun, Shaun Johnsonsh...@slugfest.demon.co.uk writes: The appended org file when exported to HTML using org-e-html (via org-export-dispatch) has brackets around the title. The generated HTML is attached (t.html) as is a screenshot (t.png). How can I avoid these brackets being inserted? Mhh.. I cannot reproduce this. Anyone else? Jambunathan has already fixed this (on the 16th). So I guess you are seeing his fix. Shaun.
Re: [O] Brackets around title in HTML from org-e-html
Shaun Johnson sh...@slugfest.demon.co.uk writes: Jambunathan has already fixed this (on the 16th). So I guess you are seeing his fix. Right, thanks for confirming. -- Bastien
Re: [O] Flexible plain list bullets
On Apr 20, 2012, at 6:19 AM, Mark E. Shoulson wrote: I guess. I spoke with someone on the IRC channel about this too, the basic idea being that the Org format should be stable, so the same file won't parse or behave differently on different installations. There's something to be said for that, but there are a fair number of customizable options that conflict with that ideal already. Some maybe should be there anyway, some might be better being made constants (or else reconsider my patch :) ). Examples: + org-emphasis-regexp-components and org-emphasis-alist are probably top candidates. These affect the parsing of Org in a pretty basic way: if you can change what characters to use for emphasis, and worse, exactly how they extend (what characters can interfere, etc), it's probably at least as potentially disruptive as alternate bullets. You might consider making these defconst instead of defcustom, if at all possible. + org-edit-src-region-extra is also a good example of exactly what you're saying shouldn't be there. First code blocks came in different ad-hoc flavors like #+ascii or lisp or whatever. Then the #+begin_src format came in order to unify them all and keep them from proliferating as new languages come up. And so all of those are quite appropriately hardcoded, just as you say they should be, in the org-edit-src-find-region-and-lang function. But that function also looks at org-edit-src-region-extra, which throws open exactly the same kind of problem you're objecting to. + org-drawers is a customization that affects structure and parsing. Notably it is also settable in-file, which anything like this really needs to be, so a file can carry its special needs with it. This is actually probably a deeper structural change than bullets, but drawers can do great things, and so may be powerful enough to be worth it. + TODO keywords and the like also affect parsing and export and cursor-movement (about the same stuff bullets would) and are settable, but again are really important and useful. The COMMENT keyword less critical, but since it's a word, it's only reasonable that people should be able to have it in the appropriate language for their file. Which does bring up one point: it isn't fair to imply that customizable bullets would not be pure plain text. Apart from the fact that they might well be used to make pure ASCII bullets (characters like @ or ! seem like possibilities), the fact is that Unicode *IS* plain text, that's what it's for. TODO keywords and such can and should be able to take on values that use non-ascii letters for users of other languages, and Org files written in Hindi or Hebrew remain pure plain text. Hi Mark, your point is well taken, but I believe that your argument is in the end not a very strong one anyway: The fact that we do have cases where the Org syntax is not completely robust and fixed cannot be an argument for adding more such cases. rant As you say, TODO keywords and DRAWERS can be set in the buffer, to make parsing stable. Using many different characters for emphasis is certainly a mistake. The main reason for the introduction of org-emphasis-alist was to make html output configurable - and even that should actually be done in a separate variable, as is done for docbook and latex backends. I have always hated myself for introducing strikethrough emphasis at all and you can find my rants about this through the years. The trouble, however, is, that once something like this has been added, it is hard to remove again. The reason for the existence of org-emphasis-regexp-components is precisely because doing the parsing correctly for a large set of emphasis delimiters is such a bitch, so I needed to play with it to get it right. But I totally agree with you, this is a prime candidate for parser incompatibility between Org files. Still, a syntax customization that changes the structure of the file (like list bullets) is heavier that if a font change goes wrong. If you look back, I was originally not for indroduction of alpha bullets, and I have often thought that stars should not have been used for this purpose because they cause ambiguity with headlines if unindented. /rant Regards - Carsten (I wonder if it would matter if the customization could only ADD possibilities, like the org-edit-src-region-extra variable does, and not replace or take away the basic ones.) ~mark On 04/19/2012 06:01 AM, Carsten Dominik wrote: On Apr 19, 2012, at 11:40 AM, suvayu ali wrote: I think this is very well put. Org must remain parsable, and all basic syntactic elements should be pure plain text and not configurable. - Carsten However, Nicolas' suggestion about a minor mode to add overlays sounds like a great idea to me. -- Suvayu Open source is the future. It sets us free. - Carsten - Carsten
Re: [O] [PATCH] Support hour in repeated task cookie
Hi Takafumi,
Takafumi Arakaki aka@gmail.com writes:
Basically, this patch changes all occurrence of [dwmy] with
[hdwmy] and adds (h . hour) to whata of org-auto-repeat-maybe.
I like this idea and I worked on a more complete patch.
I didn't replace dwmy by a constant though, this is not expected
to change anymore.
Please all test the patch and report if it breaks things or if it
is useless.
Thanks Takafumi for this idea!
From 570c927d4bc5d24567378d7643bcc1540813c705 Mon Sep 17 00:00:00 2001
From: Bastien Guerry b...@altern.org
Date: Fri, 20 Apr 2012 16:55:48 +0200
Subject: [PATCH] Support hourly repeat cookies.
* org.el (org-repeat-re)
(org-clone-subtree-with-time-shift, org-auto-repeat-maybe)
(org-deadline, org-schedule, org-matcher-time)
(org-time-stamp, org-read-date, org-read-date-get-relative)
(org-display-custom-time, org-get-wdays)
(org-time-string-to-absolute, org-closest-date)
(org-timestamp-change): Allow to set hourly repeat cookie.
Send an error when an hourly repeat cookie is set and no hour
is specified in the timestamp.
* org.texi (Repeated tasks): Document repeat cookies for
years, months, weeks, days and hours.
* org-agenda.el (org-agenda-get-timestamps): Match hourly
repeat cookies.
* org-icalendar.el (org-print-icalendar-entries): Handle
hourly repeat cookies.
Thanks a lot to Takafumi Arakaki for this idea and for a preliminary
version of this patch.
---
doc/org.texi |7 ---
lisp/org-agenda.el|2 +-
lisp/org-icalendar.el |4 ++--
lisp/org.el | 38 --
4 files changed, 27 insertions(+), 24 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index fd28352..09a8c4c 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5848,9 +5848,10 @@ or plain timestamp. In the following example
@noindent
the @code{+1m} is a repeater; the intended interpretation is that the task
has a deadline on 2005-10-01 and repeats itself every (one) month starting
-from that time. If you need both a repeater and a special warning period in
-a deadline entry, the repeater should come first and the warning period last:
-@code{DEADLINE: 2005-10-01 Sat +1m -3d}.
+from that time. You can use yearly, monthly, weekly, daily and hourly repeat
+cookies by using the @code{y/w/m/d/h} letters. If you need both a repeater
+and a special warning period in a deadline entry, the repeater should come
+first and the warning period last: @code{DEADLINE: 2005-10-01 Sat +1m -3d}.
@vindex org-todo-repeat-to-state
Deadlines and scheduled items produce entries in the agenda when they are
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index ffc27cc..7713c57 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -4962,7 +4962,7 @@ This function is invoked if `org-agenda-todo-ignore-deadlines',
(apply 'encode-time ; DATE bound by calendar
(list 0 0 0 (nth 1 date) (car date) (nth 2 date
1 11))
- \\|\\([0-9]+-[0-9]+-[0-9]+[^\n]+?\\+[0-9]+[dwmy]\\)
+ \\|\\([0-9]+-[0-9]+-[0-9]+[^\n]+?\\+[0-9]+[hdwmy]\\)
\\|\\(%%\\(([^\n]+)\\)\\)))
marker hdmarker deadlinep scheduledp clockp closedp inactivep
donep tmp priority category org-category-pos ee txt timestr tags
diff --git a/lisp/org-icalendar.el b/lisp/org-icalendar.el
index ac6a661..d322786 100644
--- a/lisp/org-icalendar.el
+++ b/lisp/org-icalendar.el
@@ -403,12 +403,12 @@ When COMBINE is non nil, add the category to each line.
(if (or (string-match org-tr-regexp hd)
(string-match org-ts-regexp hd))
(setq hd (replace-match t t hd)))
- (if (string-match \\+\\([0-9]+\\)\\([dwmy]\\) ts)
+ (if (string-match \\+\\([0-9]+\\)\\([hdwmy]\\) ts)
(setq rrule
(concat \nRRULE:FREQ=
(cdr (assoc
(match-string 2 ts)
- '((d . DAILY)(w . WEEKLY)
+ '((h . HOURLY)(d . DAILY)(w . WEEKLY)
(m . MONTHLY)(y . YEARLY
;INTERVAL= (match-string 1 ts)))
(setq rrule ))
diff --git a/lisp/org.el b/lisp/org.el
index b2b140c..95145c0 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -694,7 +694,7 @@ An entry can be toggled between QUOTE and normal with
:type 'string)
(defconst org-repeat-re
- [0-9]\\{4\\}-[0-9][0-9]-[0-9][0-9] [^\n]*?\\([.+]?\\+[0-9]+[dwmy]\\(/[0-9]+[dwmy]\\)?\\)
+ [0-9]\\{4\\}-[0-9][0-9]-[0-9][0-9] [^\n]*?\\([.+]?\\+[0-9]+[hdwmy]\\(/[0-9]+[hdwmy]\\)?\\)
Regular expression for specifying repeated events.
After a match, group 1 contains the repeat expression.)
@@ -7967,7 +7967,7 @@ and still retain the repeater to cover future instances of the task.
(if (not (and (integerp n) ( n 0)))
(error Invalid number of replications %s n))
(if (and (setq doshift (and (stringp shift) (string-match \\S- shift)))
- (not (string-match \\`[ \t]*\\+?\\([0-9]+\\)\\([dwmy]\\)[ \t]*\\'
+ (not (string-match \\`[ \t]*\\+?\\([0-9]+\\)\\([hdwmy]\\)[ \t]*\\'
shift)))
(error Invalid shift specification %s shift))
(when doshift
@@ -7985,7 +7985,7 @@ and
Re: [O] a turn-key org-mode for newbies?
I would love to do whatever I can. I'm more than happy to collect input ideas and make attempts at implementation. Please feel free to shoot your ideas/advice to the list and I'll collect them. I'd hope to have something concrete to add or review early next week. BTW, I'm currently hip-deep in an emacs24 upgrade and emacs24-starter-kit rollout. I'd expect to be using gnus through my gmail account in the near future. (Exciting stuff... no more top-posting!) Keith From: Bastien b...@altern.org To: Eric Schulte eric.schu...@gmx.com Cc: Keith Gunderson kr...@yahoo.com; emacs-orgmode@gnu.org emacs-orgmode@gnu.org Sent: Friday, April 20, 2012 8:12 AM Subject: Re: [O] a turn-key org-mode for newbies? Eric Schulte eric.schu...@gmx.com writes: Although, a simpler system based off a single Org-mode file may be preferable. Agreed. I long dreamed of an Org tutorial written with elisp source blocks, demonstrating the use of various options incrementally? Any taker? -- Bastien
Re: [O] new style of html export for documents with code blocks -- based on docco
Bastien b...@altern.org writes: Hi Eric, Eric Schulte eric.schu...@gmx.com writes: This is a simple little hack, and I don't really have time to turn it into anything more than that, but the following may be used to generate nice side-by-side docco-style exports of Org-mode documents with code blocks. http://eschulte.me/org-docco/org-docco.html Can you please add this somewhere on Worg? Thanks! I was going to, but couldn't think of a good place. If I add the actual Org-mode file to the contrib directory of the repository then I could add it to the worg/org-contrib section. Does that sound appropriate? Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Inverse matching with '/' in agenda view?
Hi! Den 19 apr 2012 16:44 skrev Michael Brand michael.ch.br...@gmail.com: ... Is a resolve in the past enough fast? ;-) It sure is! ;-) Thanks /Gustav
[O] Change example timestamps to not occur in headlines
Hi all, I've attached a small patch to the documentation that resolves a conflict between the manual's advice not to include timestamps in headlines and some of its examples where it does just that. This is the first time I've ever submitted a formal patch using git to any project, so I hope I did things the right way. Sadly, I am not presently in a position to sign assignment papers, but this is a TINYCHANGE. Best, Brian vdB 0001-Change-example-timestamps-to-not-occur-in-headlines.patch Description: Binary data
Re: [O] Drawers within inline tasks
Hi Bastien, Bastien wrote: Hi Viktor, Viktor Rosenfeld listuse...@googlemail.com writes: when I open the parent task of an inline task drawers are not folded anymore. Not sure when this regression occured. Allowing tihs was causing performance regression in `org-cycle-internal-local'. If you can provide a patch that let `org-cycle-internal-local' without any performance regression, please do. I'm afraid that my lisp-fu is not up to that. :( Cheers, Viktor
Re: [O] Change example timestamps to not occur in headlines
On Fri, Apr 20, 2012 at 11:01 AM, Brian van den Broek brian.van.den.br...@gmail.com wrote: Hi all, I've attached a small patch to the documentation that resolves a conflict between the manual's advice not to include timestamps in headlines and some of its examples where it does just that. Can you point to the discouragement? I do this and would like to know why it's discouraged but didn't see anything noting it in the manual section on dates and timestamps. Thanks, John This is the first time I've ever submitted a formal patch using git to any project, so I hope I did things the right way. Sadly, I am not presently in a position to sign assignment papers, but this is a TINYCHANGE. Best, Brian vdB
[O] Change example timestamps to not occur in headlines
Hi all,
[I wondered why my first post wasn't labelled a patch, and then I saw
that it attached as octet-stream. Investigating, I was surprised to see
that gmail's web interface cannot handle patches as attachments. Sorry
for the dupe, but I thought it best to send again in a way that
patchwork can detect.]
I've attached a small patch to the documentation that resolves a
conflict between the manual's advice not to include timestamps in
headlines and some of its examples where it does just that.
This is the first time I've ever submitted a formal patch using git to
any project, so I hope I did things the right way.
Sadly, I am not presently in a position to sign assignment papers, but
this is a TINYCHANGE.
Best,
Brian vdB
From 5ccad7cf377a19c8a8b89aba1e12c17fa96a1cb0 Mon Sep 17 00:00:00 2001
From: Brian van den Broek van...@gmail.com
Date: Fri, 20 Apr 2012 17:43:18 +0200
Subject: [PATCH] Change example timestamps to not occur in headlines
* doc/doc/org.texi Alter several examples of headings with timestamps
in them to include the timestamps in the body instead of the heading.
* b/doc/org.texi Alter the same examples in the same way as for
org.texi.
The Org-mode manual explicitly discourages the inclusion of timestamps
in headlines, yet examples do just that. These changes make the manual
consistent with its own advice.
TINYCHANGE
---
doc/org.texi | 12
doc/orgguide.texi | 12
2 files changed, 16 insertions(+), 8 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index a981f68..412a241 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5393,8 +5393,10 @@ timeline and agenda displays, the headline of an entry associated with a
plain timestamp will be shown exactly on that date.
@example
-* Meet Peter at the movies 2006-11-01 Wed 19:15
-* Discussion on climate change 2006-11-02 Thu 20:00-22:00
+* Meet Peter at the movies
+ 2006-11-01 Wed 19:15
+* Discussion on climate change
+ 2006-11-02 Thu 20:00-22:00
@end example
@item Timestamp with repeater interval
@@ -5405,7 +5407,8 @@ interval of N days (d), weeks (w), months (m), or years (y). The
following will show up in the agenda every Wednesday:
@example
-* Pick up Sam at school 2007-05-16 Wed 12:30 +1w
+* Pick up Sam at school
+ 2007-05-16 Wed 12:30 +1w
@end example
@item Diary-style sexp entries
@@ -5449,7 +5452,8 @@ angular ones. These timestamps are inactive in the sense that they do
@emph{not} trigger an entry to show up in the agenda.
@example
-* Gillian comes late for the fifth time [2006-11-01 Wed]
+* Gillian comes late for the fifth time
+ [2006-11-01 Wed]
@end example
@end table
diff --git a/doc/orgguide.texi b/doc/orgguide.texi
index f92e97b..a23a532 100644
--- a/doc/orgguide.texi
+++ b/doc/orgguide.texi
@@ -1325,8 +1325,10 @@ A simple timestamp just assigns a date/time to an item. This is just
like writing down an appointment or event in a paper agenda.
@smallexample
-* Meet Peter at the movies 2006-11-01 Wed 19:15
-* Discussion on climate change 2006-11-02 Thu 20:00-22:00
+* Meet Peter at the movies
+ 2006-11-01 Wed 19:15
+* Discussion on climate change
+ 2006-11-02 Thu 20:00-22:00
@end smallexample
@noindent @b{Timestamp with repeater interval}@*
@@ -1335,7 +1337,8 @@ applies not only on the given date, but again and again after a certain
interval of N days (d), weeks (w), months (m), or years (y). The
following will show up in the agenda every Wednesday:
@smallexample
-* Pick up Sam at school 2007-05-16 Wed 12:30 +1w
+* Pick up Sam at school
+ 2007-05-16 Wed 12:30 +1w
@end smallexample
@noindent @b{Diary-style sexp entries}@*
@@ -1360,7 +1363,8 @@ angular ones. These timestamps are inactive in the sense that they do
@emph{not} trigger an entry to show up in the agenda.
@smallexample
-* Gillian comes late for the fifth time [2006-11-01 Wed]
+* Gillian comes late for the fifth time
+ [2006-11-01 Wed]
@end smallexample
--
1.7.9
Re: [O] Change example timestamps to not occur in headlines
On 20 April 2012 18:16, John Hendy jw.he...@gmail.com wrote: On Fri, Apr 20, 2012 at 11:01 AM, Brian van den Broek brian.van.den.br...@gmail.com wrote: Hi all, I've attached a small patch to the documentation that resolves a conflict between the manual's advice not to include timestamps in headlines and some of its examples where it does just that. Can you point to the discouragement? I do this and would like to know why it's discouraged but didn't see anything noting it in the manual section on dates and timestamps. Thanks, John Hi John, The first footnote on http://orgmode.org/manual/Handling-links.html#Handling-links, for instance. There may be more, but this is the one I could find, quickly. Best, Brian vdB
Re: [O] new style of html export for documents with code blocks -- based on docco
Eric Schulte eric.schu...@gmx.com writes: Bastien b...@altern.org writes: Hi Eric, Eric Schulte eric.schu...@gmx.com writes: This is a simple little hack, and I don't really have time to turn it into anything more than that, but the following may be used to generate nice side-by-side docco-style exports of Org-mode documents with code blocks. http://eschulte.me/org-docco/org-docco.html Can you please add this somewhere on Worg? Thanks! I was going to, but couldn't think of a good place. If I add the actual Org-mode file to the contrib directory of the repository then I could add it to the worg/org-contrib section. Does that sound appropriate? Yes it does, please go ahead! Thanks, -- Bastien
Re: [O] Brackets around title in HTML from org-e-html
Bastien b...@altern.org wrote: Hi Shaun, Shaun Johnson sh...@slugfest.demon.co.uk writes: The appended org file when exported to HTML using org-e-html (via org-export-dispatch) has brackets around the title. The generated HTML is attached (t.html) as is a screenshot (t.png). How can I avoid these brackets being inserted? Mhh.. I cannot reproduce this. Anyone else? I think Jambunathan (iirc) fixed it already: 4959371 org-e-html.el: Transcode title and author correctly Nick
Re: [O] Change example timestamps to not occur in headlines
On Fri, Apr 20, 2012 at 11:18 AM, Brian van den Broek brian.van.den.br...@gmail.com wrote: On 20 April 2012 18:16, John Hendy jw.he...@gmail.com wrote: On Fri, Apr 20, 2012 at 11:01 AM, Brian van den Broek brian.van.den.br...@gmail.com wrote: Hi all, I've attached a small patch to the documentation that resolves a conflict between the manual's advice not to include timestamps in headlines and some of its examples where it does just that. Can you point to the discouragement? I do this and would like to know why it's discouraged but didn't see anything noting it in the manual section on dates and timestamps. Thanks, John Hi John, The first footnote on http://orgmode.org/manual/Handling-links.html#Handling-links, for instance. There may be more, but this is the one I could find, quickly. Gotcha. Just my take -- your patch made me think it was a major offense. The man seems to just mention that it can mess up headline linking. Not a big deal and still is a valid point, but wasn't what I expected. Thanks for the link! John Best, Brian vdB
Re: [O] Brackets around title in HTML from org-e-html
Nick Dokos nicholas.do...@hp.com writes: Bastien b...@altern.org wrote: Hi Shaun, Shaun Johnson sh...@slugfest.demon.co.uk writes: The appended org file when exported to HTML using org-e-html (via org-export-dispatch) has brackets around the title. The generated HTML is attached (t.html) as is a screenshot (t.png). How can I avoid these brackets being inserted? Mhh.. I cannot reproduce this. Anyone else? I think Jambunathan (iirc) fixed it already: 4959371 org-e-html.el: Transcode title and author correctly Yes, Shaun pointed this out -- Jambunathan is always faster than I can think :) And I'm always too confident in my ability to display the *whole* thread in Gnus... Thanks anyway! -- Bastien
[O] [PATCH] org-preview-latex-fragment not working with #+latex_header:\input{}
Bug:
#+latex_header:\input{commands.tex} is not considered in
org-preview-latex-fragment. Reason: the fragment is generated in /tmp
from where the file commands.tex can not be found. In my case,
commands.tex contains essential latex-code for displaying the
latex-fragment, so I consider this to be a bug.
I have set the environment variable TEXINPUTS in
(org-create-formula-image) to work around this bug (see patch).
However, this is the first time that I have written something like a
patch and furthermore I'm not at all familiar with lisp-programming. So
could you please have a look at my solution and tell me if it's complete
crap and how it could be done better?!
If it's no crap, I presume it should be submitted.
Thank you, Benjamin
diff --git a/org.el b/org.el.orig
index 4f5bef0..b1c15fb 100644
--- a/org.el
+++ b/org.el.orig
@@ -17040,7 +17040,6 @@ inspection.
(condition-case nil
(progn
(cd tmpdir)
- (setenv TEXINPUTS concat(default-directory :.:))
(call-process latex nil nil nil texfile))
(error nil))
(cd dir))
Re: [O] [ODT] Internal Link disparear
Michael Thanks for this report. This is a bug in the ODT exporter. I have checked in a fix to both hotfix-7.8.06 and master branch few minutes ago. I am attaching a sample Org file and the ODT file generated after the the above fix. Let me know if you have questions or run into other issues. Will appreciate if you can confirm the fix. #+TITLE: Internal Links and org-odt.el #+AUTHOR:Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DATE: 2012-04-20 Fri #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:dvipng skip:nil d:nil todo:t pri:nil tags:t #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * Preface - Hint :: To view the various links that are in this Org file do =M-x visible-mode=. - Note :: Internal links that resolve to headlines will be replaced with their section numbers. The description component of the internal links will be ignored. - Tip 1 :: Always re-save the Org-exported ODT file once it is opened in LibreOffice. This will force LibreOffice to rewrite the document. - Tip 2 :: To identify unstable or broken internal links, from within LibreOffice do, /Tools-Update-Update All/ or /Tools-Update-Fields/. Re-scan the document subsequently to identify problematic links. * One ##tag Some text. * One Dot Five :PROPERTIES: :CUSTOM_ID: one-dot-five :END: Some text. #invisible-target-in-the-middle-of-nowhere Some more text. * One Dot Seven Five Some Visible Target text. * Two 1. Section [[#tag][link]] This is a link destined for an invisible target. Note that the invisible target gets resolved (or bound) to the headline. 2. Section [[*One][One]] This is a link created with =C-c l= /(M-x org-store-link)/ and then inserting with =C-c C-l= /(M-x org-insert-link)/. See /“(info (org) Handling links)”/. 3. Section [[#one-dot-five][One Dot Five]] Link to a headline which has a /CUSTOM\_ID/. Created in the same manner as /Item (2)/. 4. Section [[One Dot Five]] This is a link created by hand. This is another way to link to a headline. 5. Click this to land in a section text - [[Visible%20Target][Visible Target]] This is a link to a visible target. Recommended way of creating them is to proceed as in /Item (2)/ but modify the /Description:/ offered at the prompt, so that the leading /file:/ component is stripped (=file:~/tmp-odt/foobar.org::Visible Target=) and just the part after =::= is used. 6. Section [[invisible-target-in-the-middle-of-nowhere][Invisible target in the middle of nothingness]] This link will be unstable. Avoid such links. foobar.odt Description: foobar.odt Hi, I am coming into a curious bug. I don’t know if it an orgmode one or an libreoffice one. When a export-as-odt the simple org file attached to this mail, and open the odt file, I obtain an odt file very «unstable»: As soon as copy and paste any text into the file, the link called link just disappear. (sometime it disappears when I’m doing some else, as a pdf export for example) If I configure LibreOffice to display the «Field Name», the name of the link is still here, OrgXref.tag, but not the link itself. It’s the first time I was using internal link into a odt org-exported file. Thanks in advance for you help. Emacs version: GNU Emacs 24.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.2.3) of 2012-04-10 on zelenka, modified by Debian Org-version: Org-mode version 7.8.06 (from debian packaging) LibreOffice Version: 3.5.2-4 (from debian packaging) -- foobar.odt Description: application/vnd.oasis.opendocument.text #+TITLE: Internal Links and org-odt.el #+AUTHOR:Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DATE: 2012-04-20 Fri #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:dvipng skip:nil d:nil todo:t pri:nil tags:t #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * Preface - Hint :: To view the various links that are in this Org file do =M-x visible-mode=. - Note :: Internal links that resolve to headlines will be replaced with their section numbers. The description component of the internal links will be ignored. - Tip 1 :: Always re-save the Org-exported ODT file once it is opened in LibreOffice. This will force LibreOffice to rewrite the document. - Tip 2 :: To identify unstable or broken internal links, from within LibreOffice do, /Tools-Update-Update All/ or /Tools-Update-Fields/. Re-scan the document subsequently to identify problematic links. * One ##tag Some text. * One Dot Five :PROPERTIES: :CUSTOM_ID: one-dot-five :END: Some text.
[O] unintended strike-through in table
When I open the following table in org, the characters from the first + symbol in +bar to the last + symbol on the next line are struck out, i.e. drawn with a line through the text. #+STARTUP: showall * foo | C | D | | E | +bar | |---+--| I do not believe this is intended behavior for +strike-through+ text. The + symbol serves triple duty in org syntax as a an indicator for +stricken words+, a line drawing symbol in tables, and a #+keyword prefix. I see little reason to continue to support +strike-through+ text. Perhaps the simplest solution would be to deprecate stricken text and disable it by default, allowing for an option to turn it on for backward compatibility.
Re: [O] new style of html export for documents with code blocks -- based on docco
Bastien b...@altern.org writes: Eric Schulte eric.schu...@gmx.com writes: Bastien b...@altern.org writes: Hi Eric, Eric Schulte eric.schu...@gmx.com writes: This is a simple little hack, and I don't really have time to turn it into anything more than that, but the following may be used to generate nice side-by-side docco-style exports of Org-mode documents with code blocks. http://eschulte.me/org-docco/org-docco.html Can you please add this somewhere on Worg? Thanks! I was going to, but couldn't think of a good place. If I add the actual Org-mode file to the contrib directory of the repository then I could add it to the worg/org-contrib section. Does that sound appropriate? Yes it does, please go ahead! Thanks, Done, see http://orgmode.org/worg/org-contrib/index.html -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Capturing to current file
If I may I'll throw in my 2 cents, since I made the error in the first place Why not in Section 9.2.1 immediately before or after the special way for using capture from the agenda? The documentation reads as follows in org-capture.el at (defun org-capture (optional goto keys) Capture something. \\org-capture-mode-map . . . When called with a `C-0' (zero) prefix, insert a template at point. . . . On 4/20/2012 8:58 AM, Bastien wrote: Hi Nick, Nick Dokosnicholas.do...@hp.com writes: Charlesmill...@verizon.net wrote: I thought that the manual states to capture a TODO to the current file use /C-0 (zero) then proceed with the capture. I use this frequently. Am I missing something in the question? Probably not - I just didn't know about this method. It's not quite a capture (no indirect buffer, no finalize) but that hardly matters. And perhaps it also does what Samuel Wales asked about, since the template can be inserted anywhere at all. BTW, I only found this with C-h f org-capture, not in the manual. If there is a place in the manual that it should be documented, can you please point at this place and suggest a change? Thanks,
Re: [O] More than one column view in a file
Hi Bastien, Bastien wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: I'd like to have a couple of different (column) views in my Org file This is currently not possible and would require a lot of work. A pity, but I completely conceive it was not clear that it could have be more promising this way (using the columns definition of the caller tree, not the callee one). Best regards, Seb -- Sebastien Vauban
Re: [O] org-program-exists vs executable-find
Hi Bastien, Bastien wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: The name `org-program-exists' is actually misleading, it should be `org-executable-call' instead, while still checking if the executable exists before calling it. Nope, the name is not misleading. The documentation string is false -- what I hadn't noticed, btw. That function just checks if the executable can be found; it does _not_ call it afterward. You're right, I just fixed the docstring. On Linux and Mac OS, it just calls which + program name, no more... On Windows, it simply fails immediately (even if the program could be found). If there is an equivalent of `which' on windows let me know, Not that I know, reason why I (must) have Cygwin... we can generalize this function. Why not replacing it simply by `executable-find': I don't see what it adds to it? I would not say so if it was some upper abstraction, but I do feel they're simply the same. If not, the opposite should be done: replacing the 10 calls to `executable-find' by calls to `org-program-exists'... Best regards, Seb -- Sebastien Vauban
Re: [O] org-program-exists vs executable-find
Hi Sebastien Vauban wxhgmqzgw...@spammotel.com writes: Hi Bastien, Bastien wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: The name `org-program-exists' is actually misleading, it should be `org-executable-call' instead, while still checking if the executable exists before calling it. Nope, the name is not misleading. The documentation string is false -- what I hadn't noticed, btw. That function just checks if the executable can be found; it does _not_ call it afterward. You're right, I just fixed the docstring. On Linux and Mac OS, it just calls which + program name, no more... On Windows, it simply fails immediately (even if the program could be found). If there is an equivalent of `which' on windows let me know, Not that I know, reason why I (must) have Cygwin... we can generalize this function. Why not replacing it simply by `executable-find': I don't see what it adds to it? I would not say so if it was some upper abstraction, but I do feel they're simply the same. If not, the opposite should be done: replacing the 10 calls to `executable-find' by calls to `org-program-exists'... Best regards, Seb IIRC on Mac OS `which' is not guaranteed to work anyway, since by default the `which database' is not instantiated or maintained. I had to kick that off manually here to have use of `which'. Best, Martyn
Re: [O] [bug] Remote durations are considered as fractions
Hi Bastien, Bastien wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: BTW, *could we limit the format of T to H:MM*, instead of H:MM:SS? The first case seems much more common, and the one used in all time clocking functions of Org. Patch welcome! I think this is it... From a77fe281afe5b568ebfd1d3969a7d4e6e8e54e63 Mon Sep 17 00:00:00 2001 From: Sebastien Vauban s...@mygooglest.com Date: Fri, 20 Apr 2012 22:43:11 +0200 Subject: [PATCH] Change output format of T specifier to H:MM * org-table.el (org-table-time-seconds-to-string): Change the format string for default output format to H:MM (instead of HH:MM:SS). --- lisp/org-table.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-table.el b/lisp/org-table.el index 2d527d7..76fa7c7 100644 --- a/lisp/org-table.el +++ b/lisp/org-table.el @@ -3319,7 +3319,7 @@ minutes or seconds. (format %.1f (/ (float secs) 60))) ((eq output-format 'seconds) (format %d secs)) - (t (org-format-seconds %.2h:%.2m:%.2s secs + (t (org-format-seconds %h:%.2m secs (defun org-table-fedit-convert-buffer (function) Convert all references in this buffer, using FUNCTION. -- 1.7.9 Best regards, Seb -- Sebastien Vauban
[O] IDE tools for maintaining Emacs Lisp programs (Org in particular)
Hello, This is a bit OT, but I'd be interested by learning how to get a better environment for editing ELisp code. Currently, the only friends I have are ElDoc and C-h f/v for navigation to symbol definitions. This is rather primitive, isn't it? When I see what CEDET and ECB seem to offer -- though I'm not using them, not coding in C/C++, etc. -- , I'm quite jealous. Questions that I have: - Do you use TAGS? - If yes, why don't we make TAGS from within the Makefile? - If yes, which ones: Emacs-style TAGS, Exuberant Ctags, GNU GLOBAL tags? - What do you use to jump from the point where a symbol is used to the point where a symbol is defined (other than using C-h f/v)? - How do you return to your previous location? - Are you able to use CEDET/ECB for Emacs Lisp? - Are you willing to share extract of your interesting configuration scraps? Best regards, Seb -- Sebastien Vauban
Re: [O] broken link in online docs
Brian van den Broek brian.van.den.br...@gmail.com writes: http://orgmode.org/manual/Tables.html#Tables has a link (see a href=../calc/index.html#TopCalc/a) that yields a 404. I finally fixed this by creating a HTML redirection. Thanks, -- Bastien
Re: [O] Flexible plain list bullets
On 04/20/2012 09:38 AM, Bastien wrote: Hi Mark, I agree with Nicolas that a solution based on overlays would be better. Probably, though very possibly not worth it. I also agree with you that there are many areas where we let the users modify the content of Org files in a way that makes them unparsable in a systematic manner. This is always a trade-off: user flexibility vs a rigid syntax. Yes. And as I noted in my examples, some/many of the cases involved were dealing with things that *really are worth* bending parsability for (as was pointed out to me on IRC.) TODO keywords, for example, *really do* have to be customizable, and the system has to deal with it. Even with global configuration variables, that in no way follow the files around. I agree that those were worth doing it for. On top of this trade-off there are many other one to consider, based on what are the available human (benevolent) resources to maintain Org. I try to prioritize things this way: 1. fix current bugs 2. improve syntax stability (against current state of flexibility) 3. extend current features 4. integrate new features Sometimes, a request raises a discussion somewhere between (3) and (2) -- which is precisely the discussion we have now. But pointing at failure in the current syntactic ground does not help promoting a feature request at (3) :) Sure. I'm just noting these because probably nobody would have seen them as issues if the importance of hard-coding the syntax hadn't come up as a point in answering me. They (probably) aren't doing much harm anyway. I'd offer to write a patch for some of the more obvious ones, to free up that much time from others, but it would be so small, it would probably take as long for someone to look over my patch as to write it themselves, so it wouldn't save anyone any time really. Pointing out a failure in the current syntactic ground does not help promoting a feature request at (3)... It might have, had the failures been so widespread as to show that this was the intended mode all along (as was not the case, so no, it doesn't). But getting the feature request in was already mostly off the table, I thought. I found some stuff that might be useful to know about; thought I should say so. (I'm talkative, yes, but not necessarily a jerk.) Also, Nicolas is working on a generic parser which will be the base for future decision on (2), and (consequently) on (3). That was mentioned, especially with respect to the source-blocks. So yes, this is complicate. We have many users. And an overlay based solution will *not* be a temporary fix, it will be something that any user can enjoy. I played with making the customization only able to ADD new characters, which I think would not be so harmful, but really only for my own edification; I can see that there really is no desire (outside me) to add this feature anyway. ~mark
Re: [O] Flexible plain list bullets
Hi Mark, Mark E. Shoulson m...@kli.org writes: I'd offer to write a patch for some of the more obvious ones, to free up that much time from others, but it would be so small, it would probably take as long for someone to look over my patch as to write it themselves, so it wouldn't save anyone any time really. Writing a patch is the only way to have someone to look over it :) And this is always a good way to encourage devs to review/apply it. And the author of the patch learns something new... we all started there. (I'm talkative, yes, but not necessarily a jerk.) :) I played with making the customization only able to ADD new characters, which I think would not be so harmful, but really only for my own edification; I can see that there really is no desire (outside me) to add this feature anyway. Don't underestimate the Unpredictable -- I'm sure if you write something with overlays and funny Unicode chars for list bullets people will start using it. Speaking for me, I'd be curious to test it! -- Bastien
Re: [O] [PATCH] org-preview-latex-fragment not working with #+latex_header:\input{}
Hi Benjamin,
Benjamin Motz b.m...@uni-muenster.de writes:
#+latex_header:\input{commands.tex} is not considered in
org-preview-latex-fragment. Reason: the fragment is generated in /tmp
from where the file commands.tex can not be found. In my case,
commands.tex contains essential latex-code for displaying the
latex-fragment, so I consider this to be a bug.
Did you try \input{/home/absolute/path/commands.tex} ?
I have set the environment variable TEXINPUTS in
(org-create-formula-image) to work around this bug (see patch).
However, this is the first time that I have written something like a
patch and furthermore I'm not at all familiar with lisp-programming. So
could you please have a look at my solution and tell me if it's complete
crap and how it could be done better?!
It complete crap and it could be done better :)
If it's no crap, I presume it should be submitted.
Setting TEXINPUTS while creating formulas makes sense to me, so I'll be
glad to have a patch for this.
Some comments:
Thank you, Benjamin
diff --git a/org.el b/org.el.orig
The diff says you are comparing org.el and org.el.orig (the original
file). With this method, it's easy to have the comparison done the
wrong way.
The *really really* simple method is to use git and Emacs =23.4.
~$ git clone git://orgmode.org/org-mode.git
Then open the .el file you want to edit. When you're done editing,
simply `C-x v ='. It will open a new buffer with the patch.
HTH,
--
Bastien
Re: [O] unintended strike-through in table
Hi Skip, Skip Collins skip.coll...@gmail.com writes: I see little reason to continue to support +strike-through+ text. Perhaps the simplest solution would be to deprecate stricken text and disable it by default, allowing for an option to turn it on for backward compatibility. I agree. If no one object, I will make this change soon. Thanks, -- Bastien
Re: [O] new style of html export for documents with code blocks -- based on docco
Eric Schulte eric.schu...@gmx.com writes: Done, see http://orgmode.org/worg/org-contrib/index.html Thanks! -- Bastien
Re: [O] More than one column view in a file
Sebastien Vauban wxhgmqzgw...@spammotel.com writes: Bastien wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: I'd like to have a couple of different (column) views in my Org file This is currently not possible and would require a lot of work. This is something I have been looking for as well and it would be a great feature, if someone feels the inspiration to work on it! However, I went on to use different specification lines and choosing the one to use by commenting the ones not to use. This is a reasonable work around until I learn enough lisp to change it. :) A pity, but I completely conceive it was not clear that it could have be more promising this way (using the columns definition of the caller tree, not the callee one). ? Regards, J -- Johnny
Re: [O] More than one column view in a file
Hi Johnny, Johnny yggdra...@gmx.co.uk writes: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: Bastien wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: I'd like to have a couple of different (column) views in my Org file This is currently not possible and would require a lot of work. This is something I have been looking for as well and it would be a great feature, if someone feels the inspiration to work on it! However, I went on to use different specification lines and choosing the one to use by commenting the ones not to use. This is a reasonable work around until I learn enough lisp to change it. :) Mhh... you made me reread Sébastien'd proposal more carefully and I now understand. If the idea is to have the choice between several column views, then it's easily feasible. I thought the question was to have several different overlays *simultaneously*... (and got half crazy by just trying to imagine this.) So, yes, let's think about this. -- Bastien
Re: [O] Yearly repeats on the agenda
Just so people know that this is a possibility: I find it useful to put inactive timestamps in headlines. This makes it simple to find entries in a sorted chronological list, and gather information about them, without any unfolding or even (in some cases) any ellipses. I think the key thing is that some people sort in the outline and other people don't. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] [PATCH] org-preview-latex-fragment not working with #+latex_header:\input{}
Hello,
** Benjamin Motz [2012-04-20 19:28:43 +0200]:
Bug:
#+latex_header:\input{commands.tex} is not considered in
org-preview-latex-fragment. Reason: the fragment is generated in /tmp
from where the file commands.tex can not be found. In my case,
commands.tex contains essential latex-code for displaying the
latex-fragment, so I consider this to be a bug.
IMHO, you doing it in wrong way, I presume you are using some Linux:
create ~/texmf/tex/latex/ben
and put there your `commands.tex', then `\input{commands.tex}' will pick
up that file.
Of course it is true for LaTeX, if you use plain TeX use
`~/texmf/tex/plain/ben' directorythen.
I have set the environment variable TEXINPUTS in
(org-create-formula-image) to work around this bug (see patch).
Don't do it. If it is Ok to use in isolated environment and only once
the TEXINPUTS variable it is bad practice.
However, this is the first time that I have written something like a
patch and furthermore I'm not at all familiar with lisp-programming. So
could you please have a look at my solution and tell me if it's complete
crap and how it could be done better?!
If it's no crap, I presume it should be submitted.
Thank you, Benjamin
diff --git a/org.el b/org.el.orig
index 4f5bef0..b1c15fb 100644
--- a/org.el
+++ b/org.el.orig
@@ -17040,7 +17040,6 @@ inspection.
(condition-case nil
(progn
(cd tmpdir)
- (setenv TEXINPUTS concat(default-directory :.:))
(call-process latex nil nil nil texfile))
(error nil))
(cd dir))
P.S. I'm using org with latex math code and all works fine (I'm using very
customized setup but it works very well).
---
WBR, Vladimir Lomov
--
I knew her before she was a virgin.
-- Oscar Levant, on Doris Day
Re: [O] [PATCH] Add svg export using pdf2svg, for latex math and src blocks.
Hi Tom, Tom Prince tom.pri...@ualberta.net writes: On Sun, 2 Oct 2011 14:35:48 -0400, Tom Prince tom.pri...@ualberta.net wrote: This is my attempt to add export of latex code (for HTML export) via svg, rather than png. I don't know if this is the best way to go about doing it, but I wanted to avoid as much duplicated code as possible. *ping* As Jambunathan said, you would need to sign FSF papers for this patch to be applied. And time passed, so the patch does not apply anymore. If you have time to work on this, that would be great. Thanks, -- Bastien
Re: [O] Agenda: Don't widen narrowed subtrees
Hi Moritz, Moritz Ulrich ulrich.mor...@googlemail.com writes: When a file used in the org-agenda is in a narrowed state (org-narrow-to-subtree or similar) and you refresh the agenda buffer via `g', it becomes un-narrowed. This is a very annoying behavior as I tend to narrow to subtrees while editing their contents. Is this a bug or desired behavior? This is a bug. It has been reported and Litvinov Sergey and Bernt Hansen tried to fix this issue. See this thread: http://thread.gmane.org/gmane.emacs.orgmode/51381/focus=51394 If the latter, I'll try hunting the missing `save-restriction' down tomorrow. A fix would be very welcome! Thanks, -- Bastien
Re: [O] [bug] Remote durations are considered as fractions
Hi Sébastien, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: I think this is it... Yes.. but in fact, this is precisely the difference between the `t' and the `T' flags - the latter displays seconds while the former display the output according to `org-table-duration-custom-format', which you can customize. Sorry I didn't mention this before. -- Bastien
Re: [O] IDE tools for maintaining Emacs Lisp programs (Org in particular)
Hi Sébastien, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: This is a bit OT, but I'd be interested by learning how to get a better environment for editing ELisp code. Currently, the only friends I have are ElDoc and C-h f/v for navigation to symbol definitions. This is rather primitive, isn't it? Well, I don't use eldoc (I should.) My setup is also quite primitive. When I see what CEDET and ECB seem to offer -- though I'm not using them, not coding in C/C++, etc. -- , I'm quite jealous. Questions that I have: - Do you use TAGS? No. - If yes, why don't we make TAGS from within the Makefile? - If yes, which ones: Emacs-style TAGS, Exuberant Ctags, GNU GLOBAL tags? - What do you use to jump from the point where a symbol is used to the point where a symbol is defined (other than using C-h f/v)? I use registers a lot. I register the point, the window configuration, I register chunks of text, etc. I also use ElScreen, which implements tabs for Emacs: http://www.emacswiki.org/emacs/EmacsLispScreen I could not actually live without ElScreen and I can't wait to use something native. - How do you return to your previous location? Usual commands (C-x C-x) and registers. - Are you able to use CEDET/ECB for Emacs Lisp? No. - Are you willing to share extract of your interesting configuration - scraps? Configuration is like hair: with age, you somehow become minimalist :) Besides using register-list.el¹, I don't have any particular setup. Sorry I can't help more! Looking forward reading other answers... Best, ¹ http://lumiere.ens.fr/~guerry/u/register-list.el -- Bastien
Re: [O] IDE tools for maintaining Emacs Lisp programs (Org in particular)
For all practical purposes, I find this be sufficient. (global-set-key (kbd C-c f) (lambda () (interactive) (require 'finder) (let ((thing (intern (thing-at-point 'symbol (if (functionp thing) (find-function thing) (find-variable thing) Put your cursor on a variable or a function, C-c f and you are staring right at the definition of the variable or function. For this to work, the library defining the function or variable should already be loaded. --
Re: [O] IDE tools for maintaining Emacs Lisp programs (Org in particular)
Jambunathan K kjambunat...@gmail.com writes: For all practical purposes, I find this be sufficient. (global-set-key (kbd C-c f) (lambda () (interactive) (require 'finder) (let ((thing (intern (thing-at-point 'symbol (if (functionp thing) (find-function thing) (find-variable thing) Put your cursor on a variable or a function, C-c f and you are staring right at the definition of the variable or function. For this to work, the library defining the function or variable should already be loaded. Just discovered this from find-func.el (require 'find-func) (find-function-setup-keys) will install the below keymap for you. It would have been more practical if these functions, made a decision of whether some symbol is a function or a variable automatically. There is also this C-x K. , | (defun find-function-setup-keys () | Define some key bindings for the find-function family of functions. | (define-key ctl-x-map F 'find-function) | (define-key ctl-x-4-map F 'find-function-other-window) | (define-key ctl-x-5-map F 'find-function-other-frame) | (define-key ctl-x-map K 'find-function-on-key) | (define-key ctl-x-map V 'find-variable) | (define-key ctl-x-4-map V 'find-variable-other-window) | (define-key ctl-x-5-map V 'find-variable-other-frame)) ` --
