[O] [BUG] Formatting of bracketed numbers in included source files
Hello, I'm experiencing issues including a file during export if that file has a single number surrounded by brackets. ,[ test.org ] | #+include: "test.py" src Python ` ,[ test.py ] | x = [1] ` With the current master (51893a4), trying to export test.org leads to the following error. , | Debugger entered--Lisp error: (error "Format specifier doesn't match argument type") | format("fn:%d-" "nil") | org-export--prepare-file-contents("/tmp/test.py" nil) | org-export-expand-include-keyword() | org-export-as(ascii nil nil nil (:ascii-charset ascii)) | org-export-to-buffer(ascii "*Org ASCII Export*" nil nil nil nil (:ascii-charset ascii) #[nil "\300 \207" [text-mode] 1]) | org-ascii-export-as-ascii(nil nil nil nil (:ascii-charset ascii)) | (lambda (a s v b) (org-ascii-export-as-ascii a s v b (quote (:ascii-charset ascii(nil nil nil nil) | org-export-dispatch(nil) | ad-Orig-call-interactively(org-export-dispatch nil nil) | call-interactively(org-export-dispatch nil nil) ` It seems that `org-export--prepare-file-contents' is treating "[1]" as a footnote. Bisecting this error suggests commit b8781c4c85f0d51cecb32e5192b5049e8f241939 introduced the issue. -- Kyle
Re: [O] Donations summary March 2014
Dear all, the donations summary from April is April 2013, a total of US$ 222.40, including $190 from Network theory for book sales. Many thanks to those who have contributed. As of a few minutes ago, I have transferred the donations to Bastien who is taking over from here on, including switching the donations button. Regards - Carsten On Mon, Mar 31, 2014 at 11:59 AM, Carsten Dominik wrote: > Dear all, > > as promised, I am going to publish a summary of Org-mode donations every > month. > > March 2014, a total of US$ 66.67 from 2 contributors > > Many thanks to those who have contributed. > > Cheers > > - Carsten >
Re: [O] Internal Links <<>> In a table
Nicolas Goaziou gmail.com> writes: > This is expected. Targets in tables return table number, but only among > captioned tables. Otherwise, the returned value is undefined. Got it. Thanks for the info. /Luke
Re: [O] Internal Links <<>> In a table
Hello, Luke Crook writes: > I just noticed that <<>> links in tables <>, <> below do not > increment, whereas <<>> links in lists do. Example below. > > > * Reference Documents > | Reference | Document Description | > |---+--| > | <>Ref-1 | Ref 1| > | <>Ref-2 | Ref 2| > | <>Ref-3 | Ref 3| > | <>Ref-4 | Ref 4| > | <>Ref-5 | Ref 5| This is expected. Targets in tables return table number, but only among captioned tables. Otherwise, the returned value is undefined. Regards, -- Nicolas Goaziou
Re: [O] Keeping up to date
I use Cask https://github.com/cask/cask for 5 machines and it works quite well if you like that style. Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi gret...@acm.org | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Tue, Apr 29, 2014 at 3:34 PM, John Hendy wrote: > On Tue, Apr 29, 2014 at 1:27 PM, Peter Davis wrote: >> Thanks, John (and Greg) for your replies. >> >> At some point, I'm going to have to bite the bullet and put all my emacs >> stuff in a Dropbox folder, so all my Macs will be in sync all the time. >> Apart from org-mode versions, I >> have inconsistencies in init files, etc. that cause me headaches. John, I'm >> inclined to agree that getting all my init stuff sync'ed is more important, >> but I think part of that is >> having all packages in one place so they're in sync as well. > > I wondered about that. Technically, it seemed you only mentioned > Emacs/Org, which I wasn't sure if that encompassed Emacs (the binary > application), other Emacs .el files, and Org, or if you just meant > keeping your Emacs binary version up to date (and Emacs doesn't rev > /that/ often). > > If you meant the former ("Emacs" meant your stash of various .el > files), then I agree that an be a headache. I'll often try some .el > program du jour, maybe keep it, maybe not, and just have them littered > about it ~/.elisp/site-lisp. Then I potentially have to add a line to > add that to my load path if it's a more involved program with it's on > dir vs. being a singular .el file. So, yes, that's a bit of a headache > as well and I think if you are doing a bunch with extra Emacs add-ons, > it would be worth syncing. > > I'm thinking I fiddle with some .el or another perhaps 2-4 times a > year, so again, it's not really impacting me. > > > John > >> >> Thanks! >> -pd >> >> >> -- >> >> Peter Davis >> The Tech Curmudgeon >> www.techcurmudgeon.com >> >
Re: [O] Organizing org-mode files: Tree view
Projectile is another option : https://github.com/bbatsov/projectile Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi gret...@acm.org | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Tue, Apr 29, 2014 at 8:36 AM, Oleh wrote: > Hi all, > >> There is a plugin for searching Org headlines: >> https://github.com/emacs-helm/helm/blob/master/helm-org.el > > There's also `worf-goto` (https://github.com/abo-abo/worf) that does > the same task as `helm-org-headlines`, and uses helm as well, but has > a better presentation, in my opinion. > > I attach two screenshots for comparison. > > regards, > Oleh
Re: [O] org-babel-lilypond newbie
Hi Grant, Another user helped me off-list--I was so unfamiliar with what I was doing that I didn't know I had to wrap the lilypond stuff in source tags to get org-mode to recognize it. Once I did that, I was up and running toward new confusions ... :) Thank you! steven Grant Rettke writes: > Does the first example here > > http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html > > work for you? > Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi > gret...@acm.org | http://www.wisdomandwonder.com/ > “Wisdom begins in wonder.” --Socrates > ((λ (x) (x x)) (λ (x) (x x))) > “Life has become immeasurably better since I have been forced to stop > taking it seriously.” --Thompson > > > On Mon, Apr 28, 2014 at 12:30 PM, Steven Arntson > wrote: >> I'm a new Lilypond user (and a beginning but dedicated Emacs user), >> trying to decide whether to use Frescobaldi or the org based "Arrange >> Mode." I think I've got Arrange Mode running, but can't seem to get the >> "tangle" command to work. I opened a .ly file I made in Frescobaldi, put >> point at the top, and run M-x ly-tangle. The message returned is >> "Tangled 0 code blocks from file-ly.ly." >> >> I'm running org 8.2.6, and have evince installed on my system (though I >> haven't told org anything about that, specifically). >> >> Thank you! >> steven arntson >> >>
Re: [O] org-babel-lilypond newbie
Does the first example here http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html work for you? Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi gret...@acm.org | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Mon, Apr 28, 2014 at 12:30 PM, Steven Arntson wrote: > I'm a new Lilypond user (and a beginning but dedicated Emacs user), > trying to decide whether to use Frescobaldi or the org based "Arrange > Mode." I think I've got Arrange Mode running, but can't seem to get the > "tangle" command to work. I opened a .ly file I made in Frescobaldi, put > point at the top, and run M-x ly-tangle. The message returned is > "Tangled 0 code blocks from file-ly.ly." > > I'm running org 8.2.6, and have evince installed on my system (though I > haven't told org anything about that, specifically). > > Thank you! > steven arntson > >
[O] Internal Links <<>> In a table
I just noticed that <<>> links in tables <>, <> below do not increment, whereas <<>> links in lists do. Example below. * Reference Documents | Reference | Document Description | |---+--| | <>Ref-1 | Ref 1| | <>Ref-2 | Ref 2| | <>Ref-3 | Ref 3| | <>Ref-4 | Ref 4| | <>Ref-5 | Ref 5| Ref-[[Ref1]], Ref-[[Ref2]], Ref-[[Ref3]] * List 1 - <> Item 1 - <> Item 2 - <> Item 3 - <> Item 4 - <> Item 5 Item-[[item1]], Item-[[item2]]. * List 2 - <> Item 1 - <> Item 2 - <> Item 3 - <> Item 4 - <> Item 5 Item-[[item6]], Item-[[item7]]
Re: [O] [RFC] Sloppy `org-element-context'?
Correcting myself: Nicolas Goaziou writes: > Bastien writes: > >> (defun org-open-links-in-comment-and-properties () >> "Open links in a comment or in a property." >> (interactive) >> (let ((string-ahead (and (looking-at ".+") (match-string 0))) >> (value (org-element-property :value (org-element-at-point >> (with-temp-buffer >> (org-mode) >> (insert value) >> (goto-char (point-min)) >> (search-forward string-ahead) >> (org-open-at-point >> >> which do work right now. > > Indeed. Actually, it will not work in comments (point is X): # Some http://orgmode.org/file.html # and http://orgmode.org/other-fileX.html The code will open the first link, not the second one. Regards, -- Nicolas Goaziou
Re: [O] Keeping up to date
On Tue, Apr 29, 2014 at 1:27 PM, Peter Davis wrote: > Thanks, John (and Greg) for your replies. > > At some point, I'm going to have to bite the bullet and put all my emacs > stuff in a Dropbox folder, so all my Macs will be in sync all the time. Apart > from org-mode versions, I > have inconsistencies in init files, etc. that cause me headaches. John, I'm > inclined to agree that getting all my init stuff sync'ed is more important, > but I think part of that is > having all packages in one place so they're in sync as well. I wondered about that. Technically, it seemed you only mentioned Emacs/Org, which I wasn't sure if that encompassed Emacs (the binary application), other Emacs .el files, and Org, or if you just meant keeping your Emacs binary version up to date (and Emacs doesn't rev /that/ often). If you meant the former ("Emacs" meant your stash of various .el files), then I agree that an be a headache. I'll often try some .el program du jour, maybe keep it, maybe not, and just have them littered about it ~/.elisp/site-lisp. Then I potentially have to add a line to add that to my load path if it's a more involved program with it's on dir vs. being a singular .el file. So, yes, that's a bit of a headache as well and I think if you are doing a bunch with extra Emacs add-ons, it would be worth syncing. I'm thinking I fiddle with some .el or another perhaps 2-4 times a year, so again, it's not really impacting me. John > > Thanks! > -pd > > > -- > > Peter Davis > The Tech Curmudgeon > www.techcurmudgeon.com >
Re: [O] struggle with using variable org-agenda-*-filter* properly
On 04/29/2014 04:51 AM, Bastien wrote: > Hi Brady, : > Filters are applied on the headlines, not on their contents, > because they are applied *after* the agenda is generated. : > Hope this clarifies things up, Yes, greatly. Thank you. Brady
[O] [PATCH] org-find-exact-heading-in-directory: Use full path
* lisp/org.el (org-find-exact-heading-in-directory): Use full path for files. When the path is not included, `org-find-exact-heading-in-directory' will fail when the current value of `default-directory' is different from the argument DIR. TINYCHANGE --- lisp/org.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index d20bb3d..24f694b 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -16133,7 +16133,7 @@ a priority cookie and tags in the standard locations." "Find Org node headline HEADING in all .org files in directory DIR. When the target headline is found, return a marker to this location." (let ((files (directory-files (or dir default-directory) - nil "\\`[^.#].*\\.org\\'")) + t "\\`[^.#].*\\.org\\'")) file visiting m buffer) (catch 'found (while (setq file (pop files)) -- 1.9.2
Re: [O] [RFC] Org Minor Mode?
Bastien writes: > We should absolutely avoid advice in code. Fully agree. (I was thinking of using an flet-like construct to temporarily rebind functions for the duration of calls, rather than permanent advice -- see elu-flet in https://github.com/notestaff/elu/blob/master/elu.el -- but, still agree.) What would be the downside of abstracting away the headline syntax in the Org code? (Other than the admittedly significant issue of disturbing well-tested core code. On the other hand, abstracted code would be more readable & maintainable; see e.g. Org syntax defined with an rx-like extension: https://github.com/notestaff/elu/blob/master/rxx-org.el , or with Thorsten's drx.el ) Obviously this would be a lot of work, but the upside of having a full Org minor mode (in particular for outshine-type use) would make it worth it, for me at least.
Re: [O] Keeping up to date
Thanks, John (and Greg) for your replies. At some point, I'm going to have to bite the bullet and put all my emacs stuff in a Dropbox folder, so all my Macs will be in sync all the time. Apart from org-mode versions, I have inconsistencies in init files, etc. that cause me headaches. John, I'm inclined to agree that getting all my init stuff sync'ed is more important, but I think part of that is having all packages in one place so they're in sync as well. Thanks! -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com
Re: [O] [babel][PATCHES] ob-R patches for review
Rainer M Krug krugs.de> writes: > > Hi > > Attached please find seven patches for review to implement the storing > of org variables in their own environment and to make the org-issued R > code look nicer in the R session. Rainer, I have suggestions and a concern. I suggest that you look at how ESS handles R objects and constructs calls in elisp to be executed in an R session. It uses a package and its NAMESPACE to provide that functionality and store objects. That makes the elisp interface a lot cleaner and keeps ESS variables out of the users way. The package is found at /etc/ESSR/. I also suggest that you introduce a customization variable to allow a user to turn off the functionality you have created. My concern is that you are injecting code into the R user session or script that the user may not want. If I already have an R object named 'org' your code will break my code. Further, all of this is hard coded, so I can't change the variable/file names. HTH, Chuck
Re: [O] Error with org-agenda-write
Hi Ian, Ian Barton writes: > The only version of the file I have on my disk is in > /home/ian/.emacs.d/src/org-mode/contrib/lisp/htmlize.el Looks like a problem with one of your (customized?) face. Can you reproduce it with emacs -Q ? -- Bastien
Re: [O] Compile error in "make pdf"
Bastien writes: >> I get a compile error when trying to run "make pdf"; see attached log >> below. >> >> Any ideas on how to fix this? > > I've updated texinfo.tex in Org to the latest stable version. Thanks, works perfectly again! All the best, Jarmo
Re: [O] Error with org-agenda-write
On 29/04/14 15:56, Bastien wrote: Hi Ian, Ian Barton writes: I haven't used this function for a while, but now get the following error. Backtrace below. I am using a recent git clone: 338e89ef163406e5714a601567415689c478df6d I am simply doing M-x org-agenda-export end entering a filename ~/agenda.html. This is a problem with htmlize.el: what version are you using? Do you use the one from the Org distribution? Hi Bastien, The only version of the file I have on my disk is in /home/ian/.emacs.d/src/org-mode/contrib/lisp/htmlize.el Ian.
Re: [O] Keeping up to date
On Tue, Apr 29, 2014 at 11:16 AM, Peter Davis wrote: > A while ago, I switched from ELPA to Git as my Org-mode source. However, I > now have three Macs I'm trying to keep in sync, and doing Git updates is > definitely more labor > intensive. Any suggestions for good ways to keep three machines all > up-to-date with Emacs and Org? If by Org, you mean the Orgmode files and not your .org files, I don't find it difficult. Once anywhere from 1x/week to 1x/month, I simply do: $ cd ~/.elisp/org.git $ git pull $ make clean && make Then again, I don't do any local branches or development, so it might be more difficult if you had files changed you'd need to merge, etc. The above could probably even be put into a script. There's also makeupN commands that I still have on my todo list to re-look into. I think those even integrate the git pull/make steps, so you'd just need to cd to your org.git repo and execute that. > I suppose the best thing would be to put all my emacs stuff in a Dropbox > folder and run from that, but I haven't managed to overcome the inertia to > get that working. The % of time that being on the bleeding edge of Org would have helped me with some issue is minimal. There are great instances where I've made a mailing list post and a change has been pushed to fix it nearly immediately. But I tend to have initiated those anyway. Thus, I really don't think most folks would notice a performance/feature benefit from updating 1x/day and 1x/month (maybe even longer). Feel free to disagree! Regarding updating Emacs, this again seems super infrequent. I'm mostly using Arch Linux, so the updates come whenever the repo changes. My Win7 work computer would be a lot more similar to keeping a Mac up to date, and I only update Emacs (aka, delete the old folder, download a new version) maybe once or twice a year. Sorry if the above was nothing new to you. Primarily, I'm trying to understand what you find very difficult or trying. Or is it just doing the above three times on separate computers that's annoying? I definitely get that, though I'd invest in sharing the same configurations between the systems before trying to get org.git and Emacs running off of dropbox. Changes to .emacs that would propagate to other computers would seem (to me, at least) *much* more impactful than keeping Org/Emacs synced. John > Org-mode is now my most heavily used emacs mode by far (though that may > change if I ever get back to coding in a "real" programming language.) > > > Thanks, > -pd > > > -- > > Peter Davis > The Tech Curmudgeon > www.techcurmudgeon.com >
Re: [O] Keeping up to date
Peter Davis writes: > A while ago, I switched from ELPA to Git as my Org-mode > source. However, I now have three Macs I'm trying to keep in sync, and > doing Git updates is definitely more labor intensive. Any suggestions > for good ways to keep three machines all up-to-date with Emacs and > Org? I use git to obtain org mode. For me, the tricky part is choosing which branch and when to update. Actually doing "git update" is easy. So I'd recommend: set "core.logallrefupdates = true" on all git repos on a well-connected server machine, clone the official repo, and checkout maint. on other machines, clone the first. when you want to update, create a tag 'stable-mmdd' on the main machine. update and ff-merge to the latest maint. Test. If you have issues, git reset --hard stable-mmdd. If you're happy, git remote update/merge (pull) on the others. That's basically what I do. I find the real work is resolving any issues From the update and deciding if it's safe. I used to follow master, not maint, so it was probably scarier there. > I suppose the best thing would be to put all my emacs stuff in a > Dropbox folder and run from that, but I haven't managed to overcome > the inertia to get that working. Do you mean your .org files or the sources for org? I don't see how git is unsuitable for the "get sources" part. I use it for .org files too (separate repo of course), and have a script to autocommit/push every morning on the main machine I edit on. One could use a distributed filesystem instead; I haven't tried the owncloud client (and wouldn't want to put any bits with confidentiality needs on dropbox). pgpKCDftJ3erw.pgp Description: PGP signature
[O] Keeping up to date
A while ago, I switched from ELPA to Git as my Org-mode source. However, I now have three Macs I'm trying to keep in sync, and doing Git updates is definitely more labor intensive. Any suggestions for good ways to keep three machines all up-to-date with Emacs and Org? I suppose the best thing would be to put all my emacs stuff in a Dropbox folder and run from that, but I haven't managed to overcome the inertia to get that working. Org-mode is now my most heavily used emacs mode by far (though that may change if I ever get back to coding in a "real" programming language.) Thanks, -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com
Re: [O] minted in Org 8.6
Hi Ken, Ken Mankoff writes: > #+begin_src emacs-lisp > ;; minted latex export > (setq org-export-latex-listings 'minted > org-export-latex-minted-options > '(("frame" "lines") > ("fontsize" "\\scriptsize") > ("linenos" ""))) > #+end_src > > If I test this with "emacs -Q", it works. If I test it with my default, > code is exported as "verbatim". This suggests the bug is in an init file > of mine. > > However, I have removed all Org sections of my init file. I am fairly > confident this is not a setting of mine, since if I look at the current > state included in a "org-submit-bug-report", the state is almost the > same between "emacs" and "emacs -Q", the only difference being Org 7.9 v. > Org 8.6, and a few default settings that have changed between the two. The new exporter, which arrived in 8.0, renamed most variables related to export. I think the variables you are setting here are now named: org-latex-listings org-latex-minted-options My guess is that renaming them in your init file will fix the problem. -- Best, Richard
Re: [O] State of the art in citations
Hi Vikas, Vikas Rawal Lists writes: > On 26-Apr-2014, at 6:56 pm, Clément B. wrote: > >> Hi all, >> >>> - Should I use biblatex instead of bibtex? >> >> You should. It is very powerful and straightforward. The manual >> is great. > > Is the choice so clearcut? > > A lot of bibliographic databases provide bibtex-compatible citation > information. How do you deal with that, when you shift to biblatex? As I recently learned (thanks to this list!), biblatex supports .bib files. So switching to biblatex is not an issue from this perspective: you can continue to drop bibtex-compatible citation information into your .bib file and use it with biblatex. If ox-bibtex reads .bib files, that should continue to work, too. Best, Richard
Re: [O] Error with org-agenda-write
Hi Ian, Ian Barton writes: > I haven't used this function for a while, but now get the following > error. Backtrace below. I am using a recent git clone: > 338e89ef163406e5714a601567415689c478df6d > > I am simply doing M-x org-agenda-export end entering a filename > ~/agenda.html. This is a problem with htmlize.el: what version are you using? Do you use the one from the Org distribution? -- Bastien
[O] minted in Org 8.6
When I export w/ the latest Org all code environments are verbatim, not minted. I'm using a test example from https://lists.gnu.org/archive/html/emacs-orgmode/2011-11/msg00585.html which is: #+begin_src emacs-lisp ;; minted latex export (setq org-export-latex-listings 'minted org-export-latex-minted-options '(("frame" "lines") ("fontsize" "\\scriptsize") ("linenos" ""))) #+end_src If I test this with "emacs -Q", it works. If I test it with my default, code is exported as "verbatim". This suggests the bug is in an init file of mine. However, I have removed all Org sections of my init file. I am fairly confident this is not a setting of mine, since if I look at the current state included in a "org-submit-bug-report", the state is almost the same between "emacs" and "emacs -Q", the only difference being Org 7.9 v. Org 8.6, and a few default settings that have changed between the two. Could this be a setting set somewhere else that is not included in the bug report? How would I find it? Or is it a bug w/ minted export in the latest Org? Thanks, -k.
[O] Error with org-agenda-write
I haven't used this function for a while, but now get the following error. Backtrace below. I am using a recent git clone: 338e89ef163406e5714a601567415689c478df6d I am simply doing M-x org-agenda-export end entering a filename ~/agenda.html. Debugger entered--Lisp error: (wrong-type-argument symbolp (fixed-pitch link)) internal-get-lisp-face-attribute((fixed-pitch link) :height nil) face-attribute((fixed-pitch link) :height) (setq h (face-attribute f :height)) (while (progn (setq f (if --cl-var-- face (face-attribute f :inherit))) (not (or (not f) (eq f (quote unspecified) (setq h (face-attribute f :height)) (setq --cl-var-- (cons (if (eq h (quote unspecified)) nil h) --cl-var--)) (setq --cl-var-- nil)) (let* ((f nil) (h nil) (--cl-var-- nil) (--cl-var-- t)) (while (progn (setq f (if --cl-var-- face (face-attribute f :inherit))) (not (or (not f) (eq f (quote unspecified) (setq h (face-attribute f :height)) (setq --cl-var-- (cons (if (eq h (quote unspecified)) nil h) --cl-var--)) (setq --cl-var-- nil)) (nreverse --cl-var--)) (progn (let* ((f nil) (h nil) (--cl-var-- nil) (--cl-var-- t)) (while (progn (setq f (if --cl-var-- face (face-attribute f :inherit))) (not (or (not f) (eq f (quote unspecified) (setq h (face-attribute f :height)) (setq --cl-var-- (cons (if (eq h (quote unspecified)) nil h) --cl-var--)) (setq --cl-var-- nil)) (nreverse --cl-var--))) (let ((size-list (progn (let* ((f nil) (h nil) (--cl-var-- nil) (--cl-var-- t)) (while (progn (setq f ...) (not ...)) (setq h (face-attribute f :height)) (setq --cl-var-- (cons ... --cl-var--)) (setq --cl-var-- nil)) (nreverse --cl-var--) (reduce (quote htmlize-merge-size) (cons nil size-list))) htmlize-face-size(org-link) (let ((size (htmlize-face-size face))) (if (eql size 1.0) nil (progn (or (and (vectorp fstruct) (>= (length fstruct) 10) (memq (aref fstruct 0) cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-size) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 3 size) (if htmlize-running-xemacs (let* ((font-instance (face-font-instance face)) (props (font-instance-properties font-instance))) (if (equalp (cdr (assq (quote WEIGHT_NAME) props)) "bold") (progn (progn (or (and (vectorp fstruct) (>= ... 10) (memq ... cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-boldp) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 4 t) (if (or (equalp (cdr (assq (quote SLANT) props)) "i") (equalp (cdr (assq (quote SLANT) props)) "o")) (progn (progn (or (and (vectorp fstruct) (>= ... 10) (memq ... cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-italicp) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 5 t) (progn (or (and (vectorp fstruct) (>= (length fstruct) 10) (memq (aref fstruct 0) cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-strikep) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 8 (face-strikethru-p face (progn (or (and (vectorp fstruct) (>= (length fstruct) 10) (memq (aref fstruct 0) cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-underlinep) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 6 (face-underline-p face) (progn (let ((--dolist-tail-- (quote (:weight :slant :underline :overline :strike-through))) attr) (while --dolist-tail-- (setq attr (car --dolist-tail--)) (let ((value (if ... ... ...))) (if (and value (not ...)) (progn (htmlize-face-emacs21-attr fstruct attr value (setq --dolist-tail-- (cdr --dolist-tail--) (let ((size (htmlize-face-size face))) (if (eql size 1.0) nil (progn (or (and (vectorp fstruct) (>= (length fstruct) 10) (memq (aref fstruct 0) cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-size) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 3 size)) (let ((fstruct (make-htmlize-fstruct :foreground (htmlize-color-to-rgb (htmlize-face-foreground face)) :background (htmlize-color-to-rgb (htmlize-face-background face) (if htmlize-running-xemacs (let* ((font-instance (face-font-instance face)) (props (font-instance-properties font-instance))) (if (equalp (cdr (assq (quote WEIGHT_NAME) props)) "bold") (progn (progn (or (and ... ... ...) (error "%s accessing a non-%s" ... ...)) (let* (...) (aset v 4 t) (if (or (equalp (cdr (assq ... props)) "i") (equalp (cdr (assq ... props)) "o")) (progn (progn (or (and ... ... ...) (error "%s accessing a non-%s" ... ...)) (let* (...) (aset v 5 t) (progn (or (and (vectorp fstruct) (>= (length fstruct) 10) (memq (aref fstruct 0) cl-struct-htmlize-fstruct-tags)) (error "%s accessing a non-%s" (quote htmlize-fstruct-strikep) (quote htmlize-fstruct))) (let* ((v fstruct)) (aset v 8 (face-strikethru-p face (progn (or (and (vectorp fstruct) (>= (length fstruct) 10) (memq (aref fstruct 0) cl-struct-html
Re: [O] (org-insert-headline '(4)) should insert new headline before point
Hi Leonard, Leonard Randall writes: > I tried it with a minimal init, having just pulled from master this > morning. It will work fine on the first line of a file. But will not > work on the second. This is what I got: > --- > * this is a test > * > this is another > --- > As I say M-Ret worked fine on the first line, but inserted a new line > when called on the second. I'm having a hard time finding out what you *did* exactly -- can you describe the way to reproduce the bug from an empty buffer, step by step? Something like 1. emacs -q 2. C-x C-f ~/test.org RET 3. [insert "bla"] 4. C-a 5. M-RET The recipe above is fine for me -- whether "bla" is on the first or the second line. Let me know, -- Bastien
Re: [O] org-reftex package and biblatex support for org-bibtex
Hi Bastien, On 29 April 2014 13:08, Bastien wrote: > > I guess so -- show us the code and we will be able to tell :) > > Thanks, I will try to get something workable by late this weekend. Also, I will let you know as soon as FSF authorizes my paperwork. All best, Leonard
Re: [O] (org-insert-headline '(4)) should insert new headline before point
Hi Bastien, I can't reproduce this, either on maint or on the master branch. > > Let me know if there is any special config that is needed to > reproduce the problem I tried it with a minimal init, having just pulled from master this morning. It will work fine on the first line of a file. But will not work on the second. This is what I got: --- * this is a test * this is another --- As I say M-Ret worked fine on the first line, but inserted a new line when called on the second. All best, Leonard On 29 April 2014 13:35, Bastien wrote: > Hi Leonard, > > Leonard Randall writes: > > > Currently, calling M-RET will create a newline before the > > text on the current line. > > I can't reproduce this, either on maint or on the master branch. > > Let me know if there is any special config that is needed to > reproduce the problem. > > Thanks, > > -- > Bastien >
Re: [O] Is OrgMode really GTD compliant?
Alan Schmitt writes: > Thanks a lot indeed. I'll fix this. I have no idea why it worked in my > case ... It half-worked: in this case (point-min) value was 1, taken from the buffer, but you really want to set POSITION at 0 -- try point-max and you'll see it raises an error. -- Bastien
Re: [O] Setting startup to "contents" does not seem to work.
On 04/29/2014 08:00 AM, Bastien wrote: Hi Nick, Nick Dokos writes: just shows the folded top-level "Foo" headlines: "Bar" and "Baz" headlines are invisible. That's not the way it's supposed to work, I think. Anybody else see that? You need to use "content", not "contents". I checked the manual and this is what is said there, but maybe we can clarify things a bit -- feel free to put a stab at it. Thanks, Ah, sorry - I looked at it repeatedly and never saw the absence of the "s". Forgive my blindness. I don't think there is anything to clarify. Thanks, Nick -- Nick
Re: [O] Is OrgMode really GTD compliant?
On 2014-04-29 15:31, Bastien writes: > Hi Samuel, > > Samuel Loury writes: > >> In that case, OBJECT is not the current buffer but a string called >> 'a'. Thus, IIUC, it makes no sense to use OBJECT=a and >> POSITION=(point-min). > > Indeed. It should be 0 in this case, thanks for spotting this, Thanks a lot indeed. I'll fix this. I have no idea why it worked in my case ... Alan
Re: [O] Is OrgMode really GTD compliant?
Hi Samuel, Samuel Loury writes: > In that case, OBJECT is not the current buffer but a string called > 'a'. Thus, IIUC, it makes no sense to use OBJECT=a and > POSITION=(point-min). Indeed. It should be 0 in this case, thanks for spotting this, -- Bastien
Re: [O] Is OrgMode really GTD compliant?
Alan Schmitt writes: > On 2014-04-29 12:30, Samuel Loury writes: >> Alan Schmitt writes: >>> On 2014-04-28 19:18, Rene writes: >>> I have not defined an Energy property, but I recently played with date >>> properties (and a user defined sorting function). If it's helpful to >>> you, the code is there: >>> https://github.com/brabalan/org-review/blob/master/org-review.el#L156 >> I looked at the code and I don't get what means the part of the code >> getting the org-marker text property of a: >> (get-text-property (point-min) 'org-marker a) >> In this part, the point-min returns the point-min of the current buffer >> (the agenda buffer in that case) while the function looks for the >> property into a. >> >> I tried launching this code into a custom agenda compare function and I >> get the error: >> Args out of range: 1197, 1197 >> This makes sense since the agenda appears to be narrowed at that time so >> that (point-min) returns 1197 and the a string at this time is not 1197 >> characters long. >> >> Replacing (point-min) by 0 appears to work (I assumed the 0th character >> of the string has the wanted text property). > > I used to have `1' instead of `point-min', but I changed it following > a suggestion from Bastien > (http://thread.gmane.org/gmane.emacs.orgmode/85217/focus=85241). Thanks for the link. I am not a good lisp hacker, so I cannot be sure of this, but I suppose Bastien did not notice the last argument 'a'. Indeed, the function is defined as: --8<---cut here---start->8--- (get-text-property POSITION PROP &optional OBJECT) Return the value of POSITION's property PROP, in OBJECT. OBJECT should be a buffer or a string; if omitted or nil, it defaults to the current buffer. If POSITION is at the end of OBJECT, the value is nil. --8<---cut here---end--->8--- Then, the POSITION argument is the position in OBJECT to look for the property. Therefore, the use of a function related to the current buffer (like point-min) seems to strongly assume that OBJECT is the current buffer (or nil). In that case, OBJECT is not the current buffer but a string called 'a'. Thus, IIUC, it makes no sense to use OBJECT=a and POSITION=(point-min). -- Konubinix GPG Key: 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A pgpO58u27dsZj.pgp Description: PGP signature
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Hi Aaron, Aaron Ecay writes: > Thanks so much for the feedback. I’ve adopted the :file-ext approach > suggested by Bastien, leaving the previous default behavior in place for > blocks with a :file argument. Looks good -- please apply in master. Thanks! PS: I assume you have commit and push access, otherwise send me your public key and I'll give it to you. -- Bastien
Re: [O] Copyright assignment
Rainer M Krug writes: > Just a minor point: If you could change it to > > Rainer M Krug Done, -- Bastien
Re: [O] Copyright assignment
Bastien writes: > Rainer M Krug writes: > >> I have received the signed copyright assignment - should I re-send the >> patches for ob-R.el? > > I added your name here: > http://orgmode.org/worg/org-contribute.html#contributors_with_fsf_papers Thanks Just a minor point: If you could change it to Rainer M Krug that would be great Rainer > > Thanks! -- 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 PGP: 0x0F52F982 pgp0K6v_lHSjO.pgp Description: PGP signature
[O] [babel][PATCHES] ob-R patches for review
Hi Attached please find seven patches for review to implement the storing of org variables in their own environment and to make the org-issued R code look nicer in the R session. Thanks, 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 PGP: 0x0F52F982 From b1199e03758f42fde2f75f02a4c18cd71fac5a03 Mon Sep 17 00:00:00 2001 From: "Rainer M. Krug" Date: Thu, 20 Mar 2014 11:35:44 +0100 Subject: [PATCH 1/8] ob-R.el: Write org variables into own R environment * lisp/ob-R.el (org-babel-expand-body:R): Create empty environment called `org' in R before adding variables and afterwards lock it and add it to the R search path. (org-babel-variable-assignments:R): Assign variables into own `org' environment in R instead of .GlobalEnv These patch implements the writing of org variables into a separate R environment and attaches it to the search path. For the usage of these variables, nothing changes in R, but: 1) The org variables are now grouped and can be seen via `ls(org)' in R and are not shown anymore in the .GlobalEnv when using `ls()' 2) As the environment `org' and all bindings are locked, the variables can not be accidentally deleted. They can be overwritten, but they can be restored by simply deleting the variable in R or by using `org$VARIABLE' instead of `VARIABLE' 3) All variables can be saved by simply calling `save(org, FILENAME' in R which makes it possible to store all variable definitions for tangling in one file. --- lisp/ob-R.el | 25 + 1 file changed, 9 insertions(+), 16 deletions(-) diff --git a/lisp/ob-R.el b/lisp/ob-R.el index 62aa7f2..82971de 100644 --- a/lisp/ob-R.el +++ b/lisp/ob-R.el @@ -103,8 +103,12 @@ this variable.") (append (when (cdr (assoc :prologue params)) (list (cdr (assoc :prologue params - (org-babel-variable-assignments:R params) - (list body) + '("try(detach(org), silent=TRUE)") + '("org <- new.env()") + (org-babel-variable-assignments:R params) + '("lockEnvironment(org)") + '("attach(org)") + (list body) (when (cdr (assoc :epilogue params)) (list (cdr (assoc :epilogue params))) (if graphics-file @@ -203,20 +207,9 @@ This function is called by `org-babel-execute-src-block'." "TRUE" "FALSE")) (row-names (if rownames-p "1" "NULL"))) (if (= max min) - (format "%s <- read.table(\"%s\", - header=%s, - row.names=%s, - sep=\"\\t\", - as.is=TRUE)" name file header row-names) - (format "%s <- read.table(\"%s\", - header=%s, - row.names=%s, - sep=\"\\t\", - as.is=TRUE, - fill=TRUE, - col.names = paste(\"V\", seq_len(%d), sep =\"\"))" - name file header row-names max -(format "%s <- %s" name (org-babel-R-quote-tsv-field value + (format "assign( '%s', read.table(\"%s\", header=%s, row.names=%s, sep=\"\\t\", as.is=TRUE ), envir = org ); lockBinding('%s', org)" name file header row-names name) + (format "assign( '%s', read.table(\"%s\", header=%s, row.names=%s, sep=\"\\t\", as.is=TRUE, fill=TRUE, col.names = paste(\"V\", seq_len(%d), sep =\"\") ), envir = org ); lockBinding('%s', org)" name file header row-names max name +(format "assign('%s', %s, envir = org); lockBinding('%s', org)" name (org-babel-R-quote-tsv-field value) name))) (defvar ess-ask-for-ess-directory) ; dynamically scoped (defun org-babel-R-initiate-session (session params) -- 1.8.5.2 (Apple Git-48) From 9b1aed4c855fd54caa7b91e316b26ef7a813b7b0 Mon Sep 17 00:00:00 2001 From: "Rainer M. Krug" Date: Wed, 26 Mar 2014 16:53:29 +0100 Subject: [PATCH 2/8] Add saving of org variable document * lisp/ob-R.el (org-babel-expand-body:R): add R command to save `org' environment after variables are stored and locked. --- lisp/ob-R.el | 1 + 1 file changed, 1 insertion(+) diff --git a/lisp/ob-R.el b/lisp/ob-R.el index 82971de..af90e68 100644 --- a/lisp/ob-R.el +++ b/lisp/ob-R.el @@ -108,6 +108,7 @@ this variable.") (org-babel-variable-assignments:R params) '("lockEnvironment(org)") '("attach(org)") + '("save(org, file='orgVARIABLES.RData')") (list body) (when (cdr (assoc :epilogue params)) (list (cdr (assoc :epilogue params))) -- 1.8.5.2 (Apple Git-48) From 27a9daaf3b94c23b437d55c5d1e3d282139ced22 Mon Sep 17 00:00:00 2001 From: "Rainer M. Krug" Date: Wed, 26 Mar 2014 17:09:15 +0100 Subjec
Re: [O] org-mobile-pull not syncing back changes
Hi Steve, Steve Dowe writes: > I seem to have a weird issue with org mobile sync. If you haven't already, perhaps you can fill an issue here: https://github.com/MobileOrg/mobileorg/issues 2 cts, -- Bastien
Re: [O] Copyright assignment
Bastien writes: > Hi Rainer, > > Rainer M Krug writes: > >> I have received the signed copyright assignment - should I re-send the >> patches for ob-R.el? > > If we are talking about this patch: > http://article.gmane.org/gmane.emacs.orgmode/83867 > > no, no need to resend the patch - but it applies on maint and not on > master, so you just need to rebuild the patch against master and let > Eric know about it for review. Thanks I will do so Rainer > > Thanks, -- 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 PGP: 0x0F52F982 pgpEoqps30c5q.pgp Description: PGP signature
Re: [O] Copyright assignment
Rainer M Krug writes: > I have received the signed copyright assignment - should I re-send the > patches for ob-R.el? I added your name here: http://orgmode.org/worg/org-contribute.html#contributors_with_fsf_papers Thanks! -- Bastien
Re: [O] (org-insert-headline '(4)) should insert new headline before point
Hi Leonard, Leonard Randall writes: > Currently, calling M-RET will create a newline before the > text on the current line. I can't reproduce this, either on maint or on the master branch. Let me know if there is any special config that is needed to reproduce the problem. Thanks, -- Bastien
Re: [O] org-bibtex-read error calling bibtex-parse-entry
Hi Mathäus, Mathäus Meyer writes: > I cannot get org-bibtex to work for me. Tried in a clean emacs -Q. Emacs- > Version: 24.4.50, org-vesion: 8.2.6 > > Calling org-bibtex-read leads, independent of the bibtex entry used on (I > tried everything, including the example of the org-bibtex-documentation), to > the following error: > > Debugger entered--Lisp error: (wrong-type-argument stringp nil) > looking-at(nil) > bibtex-parse-entry() > org-bibtex-read() > call-interactively(org-bibtex-read record nil) > command-execute(org-bibtex-read record) > execute-extended-command(nil "org-bibtex-read") > call-interactively(execute-extended-command nil nil) > command-execute(execute-extended-command) > > I am sorry if this is the wrong place, but I am not sure how to test if > bibtex-parse-entry is the real culprit. I would, of course, understand if I > cannot get help here for the pre-release snapshot of Emacs I am using. No worry, this is the right place to ask. The function `bibtex-parse-entry' is using a regular expression called `bibtex-entry-maybe-empty-head' to retrieve information from the point location about the entry to parse. The "looking-at(nil)" part of your error means this variable is not set when `bibtex-parse-entry' -- while looking at the docstring of `bibtex-entry-maybe-empty-head' I found `bibtex-set-dialect'... which leaves us with the problem of correctly setting the dialect for the buffer. I don't know where to go from there, but you surely can dig further, or someone else can help. Best, -- Bastien
Re: [O] [RFC] Org Minor Mode?
Ilya Shlyakhter writes: > What about using advice on regexp functions to transform the regexps > (when invoked in org-minor-mode buffers) so that $ is replaced with "; > $" etc? We should absolutely avoid advice in code. -- Bastien
Re: [O] putting a element +UWa in table
William Henney writes: > Assuming you never want to use strike-through text (who does?), you > can customise (or otherwise modify) the variable `org-emphasis-alist` > to remove the entry for "+". Er, yes, of course! Thanks William, -- Bastien
Re: [O] [BUG] Cannot open load file: ob-sh
Achim Gratz writes: > No, delete it. There is no reason to include it there since it is > automatically present when testing. Indeed, thanks for correcting me here, -- Bastien
Re: [O] Organizing org-mode files: Tree view
Hi Dotan, Dotan Cohen writes: > Thank you Oleh, David, and Chuck. There are some good ideas in here, > all different than what I'm looking for but still viable (actually > speedbar might be _exactly_ what I'm looking for). I'm too new to > Emacs to yet see which of them fits my needs, so I'll experiment a bit > to see what works. In your experiment, make sure you give a try to helm: http://blog.jenkster.com/2013/10/finding-files-in-emacs-helm.html https://github.com/emacs-helm/helm There is a plugin for searching Org headlines: https://github.com/emacs-helm/helm/blob/master/helm-org.el HTH, -- Bastien
Re: [O] Tried to use `org-agenda-top-headline-filter' in agenda block
Brady Trainor writes: > Please let me know if I can do anything to clarify. Providing a MWE (both the .org file to filter against and the .el for the configuration) would be great. Thanks, -- Bastien
Re: [O] org-reftex package and biblatex support for org-bibtex
Hi Leonard, Leonard Randall writes: > Let me know if you think such a package would be useful I guess so -- show us the code and we will be able to tell :) -- Bastien
Re: [O] Org version of texinfo manual
Achim Gratz writes: > I'm still in favor of doing this, but it will be an uphill battle. Trying to get .texi manuals from .org files is a good way to improve the Texinfo exporter, and the day we can export org.org to org.texi with very little headache and ad hoc configuration, yes, we will make the move. But that's a project per se and I won't be able to dedicate time to it: if you, Achim and Thomas manage to get something, I'll be more than happy! -- Bastien
Re: [O] Setting startup to "contents" does not seem to work.
Hi Nick, Nick Dokos writes: > just shows the folded top-level "Foo" headlines: "Bar" and "Baz" > headlines are invisible. That's not the way it's supposed to work, I > think. Anybody else see that? You need to use "content", not "contents". I checked the manual and this is what is said there, but maybe we can clarify things a bit -- feel free to put a stab at it. Thanks, -- Bastien
Re: [O] Copyright assignment
Hi Rainer, Rainer M Krug writes: > I have received the signed copyright assignment - should I re-send the > patches for ob-R.el? If we are talking about this patch: http://article.gmane.org/gmane.emacs.orgmode/83867 no, no need to resend the patch - but it applies on maint and not on master, so you just need to rebuild the patch against master and let Eric know about it for review. Thanks, -- Bastien
Re: [O] struggle with using variable org-agenda-*-filter* properly
Hi Brady, Brady Trainor writes: > ;; (org-agenda-regexp-filter-preset '(":STYLE:.+habit")) > ;; (org-agenda-tag-filter-preset '("+STYLE=\"habit\"")) Filters are applied on the headlines, not on their contents, because they are applied *after* the agenda is generated. That's why the first filter above will not work. Also, "tag" in "org-agenda-tag-filter-preset" means "tag", not a tag-and/or-property-query. So it should be something like this (org-agenda-tag-filter-preset '("mytag")) to filter a headline containing the tag "mytag". Hope this clarifies things up, -- Bastien
Re: [O] Compile error in "make pdf"
Hi Jarmo, Jarmo Hurri writes: > I get a compile error when trying to run "make pdf"; see attached log > below. > > Any ideas on how to fix this? I've updated texinfo.tex in Org to the latest stable version. Hopefully this does not break backward compatibility for those who still want to use Texinfo 4.x for speed reasons. Otherwise, commenting out @set txicodequoteundirected @set txicodequotebacktick will do. Thanks for reporting this, -- Bastien
Re: [O] Organizing org-mode files: Tree view
Thank you Oleh, David, and Chuck. There are some good ideas in here, all different than what I'm looking for but still viable (actually speedbar might be _exactly_ what I'm looking for). I'm too new to Emacs to yet see which of them fits my needs, so I'll experiment a bit to see what works. Thank you. -- Dotan Cohen http://gibberish.co.il http://what-is-what.com
Re: [O] State of the art in citations
> Hi all, > >> - Should I use biblatex instead of bibtex? > > You should. It is very powerful and straightforward. The manual > is great. > ox-bibtex provides a usable implementation of including bibtex citations in html export. Can this be done if using biblatex? Vikas
Re: [O] [PATCH] Fix: Capture abort: (error: The mark is not set now, so there is no region)
Hi Alex, Alex Kosorukoff writes: > I noticed a regression in the capture functionality after upgrading > org. Capture fails with error in subj fixed, thanks, -- Bastien
Re: [O] Is OrgMode really GTD compliant?
Hi Samuel, On 2014-04-29 12:30, Samuel Loury writes: > Hi, > Alan Schmitt writes: > >> On 2014-04-28 19:18, Rene writes: >> I have not defined an Energy property, but I recently played with date >> properties (and a user defined sorting function). If it's helpful to >> you, the code is there: >> https://github.com/brabalan/org-review/blob/master/org-review.el#L156 > I looked at the code and I don't get what means the part of the code > getting the org-marker text property of a: > (get-text-property (point-min) 'org-marker a) > In this part, the point-min returns the point-min of the current buffer > (the agenda buffer in that case) while the function looks for the > property into a. > > I tried launching this code into a custom agenda compare function and I > get the error: > Args out of range: 1197, 1197 > This makes sense since the agenda appears to be narrowed at that time so > that (point-min) returns 1197 and the a string at this time is not 1197 > characters long. > > Replacing (point-min) by 0 appears to work (I assumed the 0th character > of the string has the wanted text property). I used to have `1' instead of `point-min', but I changed it following a suggestion from Bastien (http://thread.gmane.org/gmane.emacs.orgmode/85217/focus=85241). > Incidentally, I don't manage to have edebug triggered in a custom org > agenda cmp function. I load the function with C-u C-M-x. the message > "Edebug: org-energy-compare" appears as usual. When I launch the agenda > I can see the function has been called since the entries are correctly > sorted. But I was never given the input to debug it. Do you know why? I'm curious about this as well. I've had little luck in getting edebug to launch when I'm creating agenda views. Alan
[O] Compile error in "make pdf"
Greetings. After updating to Fedora 20 and the latest TeXLive available: TeX 3.1415926 (TeX Live 2013) kpathsea version 6.1.1 and with the latest org from git: release_8.2.6-928-gec0eab7 I get a compile error when trying to run "make pdf"; see attached log below. Any ideas on how to fix this? All the best, Jarmo make -C doc pdf make[1]: Entering directory `/home/jarmo/src/org-mode/doc' texi2pdf --batch --clean --expand orgguide.texi -:86: @menu seen before first @node -:86: perhaps your @top node should be wrapped in @ifnottex rather than @ifinfo? -:105: @detailmenu seen before first @node -:105: perhaps your @top node should be wrapped in @ifnottex rather than @ifinfo? -:1918: @itemx must follow @item -:1922: @itemx must follow @item -:225: Prev reference to nonexistent `Top' -:225: Up reference to nonexistent `Top' -:298: warning: unreferenced node `Document Structure' -:298: Up reference to nonexistent `Top' -:567: warning: unreferenced node `Tables' -:567: Up reference to nonexistent `Top' -:691: warning: unreferenced node `Hyperlinks' -:691: Up reference to nonexistent `Top' -:835: warning: unreferenced node `TODO Items' -:835: Up reference to nonexistent `Top' -:1089: warning: unreferenced node `Tags' -:1089: Up reference to nonexistent `Top' -:1249: warning: unreferenced node `Properties' -:1249: Up reference to nonexistent `Top' -:1310: warning: unreferenced node `Dates and Times' -:1310: Up reference to nonexistent `Top' -:1534: warning: unreferenced node `Capture - Refile - Archive' -:1534: Up reference to nonexistent `Top' -:1693: warning: unreferenced node `Agenda Views' -:1693: Up reference to nonexistent `Top' -:2056: warning: unreferenced node `Markup' -:2056: Up reference to nonexistent `Top' -:2295: warning: unreferenced node `Exporting' -:2295: Up reference to nonexistent `Top' -:2431: warning: unreferenced node `Publishing' -:2431: Up reference to nonexistent `Top' -:2478: warning: unreferenced node `Working With Source Code' -:2478: Up reference to nonexistent `Top' -:2594: warning: unreferenced node `Miscellaneous' -:2594: Next reference to nonexistent `GNU Free Documentation License' -:2594: Up reference to nonexistent `Top' This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013) restricted \write18 enabled. entering extended mode (/home/jarmo/src/org-mode/doc/orgguide.t2d/pdf/src/orgguide.texi (/home/jarmo/src/org-mode/doc/texinfo.tex Loading texinfo [version 2012-01-03.18]: pdf, fonts, page headings, tables, conditionals, indexing, sectioning, toc, environments, defuns, macros, cross references, insertions, (/home/jarmo/texlive/2013/texmf-dist/tex/generic/epsf/epsf.tex This is `epsf.tex' v2.7.4 <14 February 2011> ) localization, formatting, and turning on texinfo input format.) /home/jarmo/src/org-mode/doc/orgguide.t2d/pdf/src/orgguide.texi:12: Undefined c ontrol sequence. l.12 @codequoteundirected on /home/jarmo/src/org-mode/doc/orgguide.t2d/pdf/src/orgguide.texi:13: Undefined c ontrol sequence. l.13 @codequotebacktick on [1{/home/jarmo/texlive/2013/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2] [-1] Chapter 1 Cross reference values unknown; you must run TeX again. Chapter 2 [1] [2] [3] [4] Chapter 3 [5] [6] Chapter 4 [7] [8] Chapter 5 [9] [10] [11] [12] Chapter 6 [13] [14] Chapter 7 [15] Chapter 8 [16] [17] [18] Chapter 9 [19] [20] Chapter 10 [21] [22] [23] [24] [25] [26] Chapter 11 [27] [28] [29] Chapter 12 [30] [31] Chapter 13 [32] Chapter 14 [33] [34] Chapter 15 [35] [36] ) (see the transcript file for additional information) Output written on orgguide.pdf (39 pages, 311912 bytes). Transcript written on orgguide.log. /usr/bin/texi2dvi: pdftex exited with bad status, quitting. make[1]: *** [orgguide.pdf] Error 1 make[1]: Leaving directory `/home/jarmo/src/org-mode/doc' make: *** [pdf] Error 2
Re: [O] org-store-link dired and files with spaces
Hello, Bart Bunting writes: > I'm having an issue with storing links to files with spaces in their > names. > > If I visit a dired buffer, use c-c l to store the link of the file under > point and then in an org buffer c-c c-l to insert it. > > I find that the file can not be opened from within the org buffer as org > appears to not recognize spaces in the file name and only sees the > filename as the part up until the first space. > > An example of a link that does not work: > > [[file:resumes/Sandeep%20Salwan%20Satellite%20network%20engineer%20Cover%20Letter.doc][file:resumes/Sandeep > Salwan Satellite network engineer Cover Letter.doc]] What Org version are you using? I cannot reproduce it with master. > I don't quite understand why the first part of the link (the > description) is url encoded but not the latter part? The description is for human consumption. It doesn't need to be encoded. To tell the truth, it can be troublesome if the file name contains square brackets, but I don't think we need to impede readability to work around this. Regards, -- Nicolas Goaziou
Re: [O] Is OrgMode really GTD compliant?
Hi, Alan Schmitt writes: > On 2014-04-28 19:18, Rene writes: > I have not defined an Energy property, but I recently played with date > properties (and a user defined sorting function). If it's helpful to > you, the code is there: > https://github.com/brabalan/org-review/blob/master/org-review.el#L156 I looked at the code and I don't get what means the part of the code getting the org-marker text property of a: --8<---cut here---start->8--- (get-text-property (point-min) 'org-marker a) --8<---cut here---end--->8--- In this part, the point-min returns the point-min of the current buffer (the agenda buffer in that case) while the function looks for the property into a. I tried launching this code into a custom agenda compare function and I get the error: --8<---cut here---start->8--- Args out of range: 1197, 1197 --8<---cut here---end--->8--- This makes sense since the agenda appears to be narrowed at that time so that (point-min) returns 1197 and the a string at this time is not 1197 characters long. Replacing (point-min) by 0 appears to work (I assumed the 0th character of the string has the wanted text property). My first guess of an energy cmp function is: --8<---cut here---start->8--- (defun org-energy-compare (a b) (let* ( (ma (or (get-text-property 0 'org-marker a) (get-text-property 0 'org-hd-marker a))) (mb (or (get-text-property 0 'org-marker b) (get-text-property 0 'org-hd-marker b))) (energy_a (org-entry-get ma "Energy")) (energy_b (org-entry-get mb "Energy")) ) (cond ((and (not energy_a) (not energy_b) ) nil ) ((and energy_a (not energy_b) ) 1 ) ((and (not energy_a) energy_b ) -1 ) ((> energy_a energy_b) 1 ) ((< energy_a energy_b) -1 ) (t nil ) ) ) ) --8<---cut here---end--->8--- Incidentally, I don't manage to have edebug triggered in a custom org agenda cmp function. I load the function with C-u C-M-x. the message "Edebug: org-energy-compare" appears as usual. When I launch the agenda I can see the function has been called since the entries are correctly sorted. But I was never given the input to debug it. Do you know why? -- Konubinix GPG Key: 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A pgpGnBb1TO42j.pgp Description: PGP signature
Re: [O] State of the art in citations
On 26-Apr-2014, at 6:56 pm, Clément B. wrote: > Hi all, > >> - Should I use biblatex instead of bibtex? > > You should. It is very powerful and straightforward. The manual > is great. > Is the choice so clearcut? A lot of bibliographic databases provide bibtex-compatible citation information. How do you deal with that, when you shift to biblatex? Of course, this is not an org-mode specific limitation at all. But still relevant, I think, when we are discussing what should be the recommended way of dealing with citations in org-mode. Vikas
Re: [O] org-bbdb link completion fix
Hello, Eric Abrahamsen writes: > Nicolas Goaziou writes: > >> Thank you for the patch. Would you mind providing a proper commit >> message and send it again? > > Yup, sorry about that. Patch applied. Thank you. Regards, -- Nicolas Goaziou