Re: [O] Org-lint -- Lisp error: (wrong-type-argument arrayp nil)
Nicolas Goaziou writes: Fabrice Niessen writes: Though, there is one error with which I don't agree: 367 high Missing colon in header argument ) where line 367 is indicated by : Are you sure you are using the latest wip-lint? It should be fixed already (commit 406cfbf2a148c4ea98278603ed5b096bbcdd5370, cherry-picked from master). It *is* fixed. I guess I switched to the correct branch, but forgot the git pull... Sorry for the noise. And thanks for org-lint which spotted a real missing : in some PROPERTY drawer. Hard to see afterward... Best regards, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] Tangling takes long - profiling and calling R
Aaron Ecay aarone...@gmail.com writes:
Could you take a look at
http://mid.gmane.org/87fvg07vzi.fsf@Rainer.invalid, specifically the
paragraph beginning “That looks like a bug”?
This should be fixed in 188bae903feb942355dae6878951e9f13211e1d0. Thank
you for the notice.
I don’t want to argue the semantics excessively, but “deprecated” should
mean that users:
1) actually change their behavior when creating new documents, or at
least
2) are aware that the old behavior is in danger of disappearing.
A footnote in the manual and a comment in the elisp file don’t really
achieve this, as evidenced by the periodic discussions of this point that
we have.
This is why I suggest to also announce the deprecation in ORG-NEWS, then
effectively remove it in the next release.
Additionally, last year Eric commented that the deprecation was
“premature” http://article.gmane.org/gmane.emacs.orgmode/87739. This
arguably means (among other things) that more effort to publicize it and
work on its replacement is needed, something that has not really
happened.
Let's move forward and discuss about what is needed then.
Neither syntax is necessary, by this metric. We could just make do with
local arguments, not needing properties at all.
IOW, this doesn’t distinguish between these two approaches.
You may be misunderstanding me. I don't want to distinguish between
these approaches. Both are certainly fine, but two of them in one too
many. This is just confusing and more difficult to maintain.
I suggest to remove the old dynamic setting and improve the new
lexical one, if needed.
The dynamic vs. lexical metaphor is not very helpful either.
It doesn't matter. Let's call one the old setting and the other the
recent setting. Or tag them A and B.
There has been no justification for the new property system proposed
other than questions of taste such as the above, and efficiency. The
efficiency considerations could be solved in several ways. One obvious
one would be to use a single call to org-entry-properties rather than N
calls to org-entry-get. I feel like a broken record saying this, but it
was a solution I suggested already, in the last thread
http://mid.gmane.org/87r3zlrcnt@gmail.com. Another, more
ambitious, solution would be to use the parser cache for
org-entry-{properties,get}. There was a patch for this
http://article.gmane.org/gmane.emacs.orgmode/89326, which never landed
for a variety of reasons.
I don't think efficiency is a matter here. `org-entry-get' is reasonably
fast nowadays (since properties drawers change), even using inheritance.
Regards,
Re: [O] Maybe 1st ox-texinfo manual in the wild
org manual in org-mode That's very cool! I wonder why the official Org Manual source is not in org-mode. -- Kaushal Modi On Jul 3, 2015 7:08 AM, Eric Abrahamsen e...@ericabrahamsen.net wrote: Rasmus ras...@gmx.us writes: Hi, The magit 2.1 manual was typeset using ox-texinfo, it seems. Neat. Very cool! And this is a perfect opportunity to repost the link to Tom's org-manual-in-org, which I mostly keep around because it's a great example of how to do texinfo in the Org source. Good indexing is what keeps Info relevant! And what a relief to be able to do it in Org. https://raw.githubusercontent.com/tsdye/orgmanual/master/orgmanual.org
Re: [O] Paste from clip/kill ring as cold block?
This sounds like s tab type language enter C-y Or if you know the language use the right shortcut first. E.g. I use p for python and el for emacs lisp. You could use a function for that but there are only 5 key strokes plus the keys for the language above! The function name would probably be longer. On July 3, 2015, at 5:44 AM, Xebar Saram zelt...@gmail.com wrote: Hi list i use code block alot in my various org mode users. while the C-c C-v d is fast to use i find that alot of my use cases are focused on pasting stuff and then converting that into code blocks. i was wondering if anyone knew or uses his own mini script of a way to paste from the clipboard/killring as a code block? ie if i have XYZ in the clip it would paste as #+BEGIN_SRC emacs-lisp XYZ #+END_SRC maybe one could use hydra to choose which language to paste as code just an idea, would love to hear if anyone is using something similar best Z
Re: [O] ELisp expression in a var not executed anymore on tangle
Hello,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
I noticed that the following code block:
#+begin_src shell :tangle yes :var workingDir=(file-name-directory (or
load-file-name (buffer-file-name))) :shebang #!/bin/sh
cmd=$EMACS -q -l ${workingDir}init.el
#+end_src
does now return this:
#!/bin/sh cmd=$EMACS -q -l ${workingDir}init.el
instead of:
#!/bin/sh
workingDir='d:/Users/sva/ecm/'
cmd=$EMACS -q -l ${workingDir}init.el
IIRC, you can also see that it's not working by pressing `C-c C-v C-v'
(preview).
This should be fixed in 048f0e1a82cbb9fa29aa5ad8c778b1a72fc59fda. Thank
you.
Regards,
--
Nicolas Goaziou
Re: [O] Extract document structure from Org file
That sounds really cool. I recently hacked a swish-e index of my org files (there might have been 3000+!) http://kitchingroup.cheme.cmu.edu/blog/2015/06/25/Integrating-swish-e-and-Emacs/. and I just updated it to index the html version of an org-file so that I take advantage of the structure in the search. http://kitchingroup.cheme.cmu.edu/blog/2015/07/03/Using-swish-e-to-index-org-files-as-html/. It would be cool to have more granular searching though. Is your info project visible anywhere? i can imagine a close-file hook function that updates the database automatically. Oleg Sivokon writes: Hello list! Suppose I wanted to extract the structure from an Org document, where, what's important for me would be to have it cathegorically divided into headers, paragraphs of text, technical information and inclusion of other documents (code snippets). How would I do it? The reason I'm asking is that I've a small project I work on, where I'm trying to enhance the search in documents by using indexing combined with queries based on things like distance between words, frequency of a word appearing in a document and so on. (I'm using Sphinx for it.) I've tried to do this with Info pages, and I liked the results, however, in order to do this more intelligently, I'd like to index the documents with better granularity (i.e. so that later on I could search assigning different weights to words appearing in headers and words appearing in comments). Best. Oleg -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] [patch, ox-latex] caption and :float nil
Rasmus ras...@gmx.us writes: Pushed. Thank you. Regards,
Re: [O] Structuring and (cross)linking information in org-mode
This all sounds doable, but it will take some work ;) I know how to make tasks with the org-todo-keywords. Now I want to mark chunks of information in that file in a similar way, but keep it outside of the task workflow. I’d like to have that information accessible and finable easily, and I want to differentiate different kinds of information. Quick example: * TODO This is my first task Some task description goes here * MEETINGNOTE of meeting 2015-07-02 MyCompany I think you should probably use a tag of :MEETINGNOTE: here, instead of a TODO keyword like this. TODO keywords imply to me some kind of changeable state not a type of content. Alteratively you could make it a property. with your curson on the headline, type C-c C-c and enter MEETINGNOTE to add the tag. ** participants *** — John Doe *** — Mary Sample ** Goal This is the description of meeting goal ** Outcome Outcome of the meeting * PERSON John Doe Street address email address telephone PERSON should also be a tag, or look at org-contacts, where those bits in the body would be stored as properties. * COMPANY MyCompany address field of operation employees: - John Doe - Mary Sample * INFO 2015-07-01 John Doe does not want to work with Emacs You should use org dates like [2015-07-01] which will make them clickable. I think INFO here should be a tag too. * NOTE 2015-07-02 16:20 called John on the phone here go some notes about the telephone call with John So for example: - I’d like to have all the info (cross)linked, so that if I click e.g. on any occurrence of „John Doe“ I’d like to see a list of matches that mention John Doe: his PERSON entry, the notes of meetings he participated, the company he is an employee of etc. How can I mark up info in a way that Emacs or org links such info? Or isn’t this possible? Do I have to use Gnowsys or something like that for this? This is not totally possible, org-mode does not know how to make John Doe clickable unless you make a special link. but see: http://kitchingroup.cheme.cmu.edu/blog/2015/06/22/Clickable-org-contacts-in-text-files/ - I’d like to be able to search all „PERSON“ entries for a specific name. See org-contacts. i integrated something like this into helm: http://kitchingroup.cheme.cmu.edu/blog/2015/03/14/A-helm-mu4e-contact-selector/ which I use all the time. - I’d like to be able to archive chunks of information, e.g. a MEETINGNOTE that’s obsolete, equally as I can do it with tasks C-c C-x a will archive a headline. you can only archive headlines, not pieces of text. - I’d like to filter, i.e. have Emacs only show me e.g. the „MEETINGNOTES“ entries with all their text, but filter out everything else. Maybe even only „MEETINGNOTES“ with tag „XY“… combined filtering. Possible via Agenda, as I understand it, at least partially. Matching tags and combinations of tags etc. This sounds pretty doable with tag/property searches. Fot those of you who owned (or still own) a HP 200LX Palmtop and use Andreas Garzotto’s excellent PIM/PE on it (PE was a text editor that was partially inspired by Emacs and PIM was quite similar to org-mode, although PIM existed prior to org-mode): I’d like to do something similar with Emacs / org that was possible with PIM/PE. :-) Thanks for any hints, pointers and ideas, Daniel -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] [patch, ox-latex] caption and :float nil
I updated the patches. Pushed. Thanks, Rasmus -- Hvor meget poesi tror De kommer ud af et glas isvand?
Re: [O] Structuring and (cross)linking information in org-mode
I think properties can be used for this. I personally like the org-secretary module, described nicely here by the author: http://juanreyero.com/article/emacs/org-teams.html Also, personalized agendas http://orgmode.org/manual/Storing-searches.html#Storing-searches for your entire set of org-files is useful here. --paf On Fri, Jul 3, 2015 at 10:47 AM, Daniel Hertrich daniel@daniel-hertrich.photo wrote: Hi all, I’m new to this mailing list and very eager to see what’s up in here. Is it still active? I hope so. Emacs is old, but it seems that still many people use it. So am I. After trying many different approaches to organizing information and tasks, I’m now looking into Emacs / org-mode, because I like the efficient keyboard-centric text-mode way of working. One question that I did not find a satisfactory answer for on my numerous days of research about Emacs / org-mode (however, maybe I „don’t see the wood for the trees“): I want to mix information and tasks in one file. That’s how it’s supposed to be, as far as I understand. I want to enter information as a journal, relatively strictly. So if I add a note to an appointment, I’d like to add that note not in the file area of that appointment, but to the end of the file, crosslinking the appointment and the new note. Is there a way to achieve that easily? I know how to make tasks with the org-todo-keywords. Now I want to mark chunks of information in that file in a similar way, but keep it outside of the task workflow. I’d like to have that information accessible and finable easily, and I want to differentiate different kinds of information. Quick example: * TODO This is my first task Some task description goes here * MEETINGNOTE of meeting 2015-07-02 MyCompany ** participants *** — John Doe *** — Mary Sample ** Goal This is the description of meeting goal ** Outcome Outcome of the meeting * PERSON John Doe Street address email address telephone * COMPANY MyCompany address field of operation employees: - John Doe - Mary Sample * INFO 2015-07-01 John Doe does not want to work with Emacs * NOTE 2015-07-02 16:20 called John on the phone here go some notes about the telephone call with John So for example: - I’d like to have all the info (cross)linked, so that if I click e.g. on any occurrence of „John Doe“ I’d like to see a list of matches that mention John Doe: his PERSON entry, the notes of meetings he participated, the company he is an employee of etc. How can I mark up info in a way that Emacs or org links such info? Or isn’t this possible? Do I have to use Gnowsys or something like that for this? - I’d like to be able to search all „PERSON“ entries for a specific name. - I’d like to be able to archive chunks of information, e.g. a MEETINGNOTE that’s obsolete, equally as I can do it with tasks - I’d like to filter, i.e. have Emacs only show me e.g. the „MEETINGNOTES“ entries with all their text, but filter out everything else. Maybe even only „MEETINGNOTES“ with tag „XY“… combined filtering. Possible via Agenda, as I understand it, at least partially. Matching tags and combinations of tags etc. Fot those of you who owned (or still own) a HP 200LX Palmtop and use Andreas Garzotto’s excellent PIM/PE on it (PE was a text editor that was partially inspired by Emacs and PIM was quite similar to org-mode, although PIM existed prior to org-mode): I’d like to do something similar with Emacs / org that was possible with PIM/PE. :-) Thanks for any hints, pointers and ideas, Daniel
[O] help with MWE error: Variable binding depth exceeds max-specpdl-size
Hello, Using the latest git HEAD (048f0), I am trying to make a MWE for another problem however, can someone please tell me what is missing from the init file because I get an error when I press TAB in the table. Starting emacs like this: $ emacs a.org -Q -l init.el with these files: a.org - * x | a | |---| | 1 | init.el --- (setq debug-on-error t) (add-to-list 'load-path ~/.emacs.d/plugins/org-mode/lisp) (add-to-list 'load-path ~/.emacs.d/plugins/org-mode/contrib/lisp t) (require 'org) ;;(require 'org-index) I get this traceback: Debugger entered--Lisp error: (error Variable binding depth exceeds max-specpdl-size) outline-on-heading-p(t) org-at-heading-p() org-element--current-element(23 element nil nil) byte-code(`\212\306\307 \211\310P\311 \210,`)\312\211\211\211\211\211\211 *+,-./\306\307 \211\310 P\313 \203Teb\210\314 \210m\204L\315 /V\203\205\316\317\312\\210\202\205\320 \210\312y\210\314 \210m\204i\315 /V\203\205\316\317\321\312x\210\322 \2100\204~\323d\306\\202\203\323d\306\C\\210,\322 \210\324.\325,*$\211@-\326\f12\211;\203\263\327\31221$\202\304A\330A@21#\240\210+\2100\203\322+B+\3312;\203\351\332\3332#\202\361\334A@2\*\2113/W\204\f3/U\2053.U?\2053b)\204\211-4\204.\316\3170\203'+\202)\\210\202\211\3352;\203E\332\3332#\202M\334A@2\*\3362;\203e\332\3332#\202m\334A@2\*5\2116\203\2745\203\2746/V\204\2745/W\204\2746/U\203\232-\337\204\2745/U\203\317-\340\204\274-\341\203\3175b\210n\204\274m\204\317\316\3170\203\310+\202\312\\210\202@\342-\343\\203\344,\3452;\203\364\332\3332#\202\374\334A@2\**\2028\342-\344\\203\312,\2028\342-\346\\203!\347,\312*\2028\342-\350\\2032\351,\312*\2028\312\211,*5.6b\210*\202\211 [org-called-with-limited-levels org-outline-regexp outline-regexp org-outline-regexp-bol parent prevs t org-get-limited-outline-regexp ^ outline-next-heading nil org-before-first-heading-p org-skip-whitespace line-beginning-position throw exit org-back-to-heading \n beginning-of-line org-element-headline-parser org-element--current-element element :parent org-add-props plist-put :end get-text-property 0 plist-get :contents-begin :contents-end (plain-list table) (center-block drawer dynamic-block inlinetask property-drawer quote-block special-block) (item plain-list) eql plain-list item :structure property-drawer node-property table table-row struct trail special-flag type end origin keep-trail value ...] 10) org-element-at-point() org-table-begin(any) org-at-table\.el-p() org-element-table-parser(23 (5)) org-element--current-element(23 element nil nil) byte-code(`\212\306\307 \211\310P\311 \210,`)\312\211\211\211\211\211\211 *+,-./\306\307 \211\310 P\313 \203Teb\210\314 \210m\204L\315 /V\203\205\316\317\312\\210\202\205\320 \210\312y\210\314 \210m\204i\315 /V\203\205\316\317\321\312x\210\322 \2100\204~\323d\306\\202\203\323d\306\C\\210,\322 \210\324.\325,*$\211@-\326\f12\211;\203\263\327\31221$\202\304A\330A@21#\240\210+\2100\203\322+B+\3312;\203\351\332\3332#\202\361\334A@2\*\2113/W\204\f3/U\2053.U?\2053b)\204\211-4\204.\316\3170\203'+\202)\\210\202\211\3352;\203E\332\3332#\202M\334A@2\*\3362;\203e\332\3332#\202m\334A@2\*5\2116\203\2745\203\2746/V\204\2745/W\204\2746/U\203\232-\337\204\2745/U\203\317-\340\204\274-\341\203\3175b\210n\204\274m\204\317\316\3170\203\310+\202\312\\210\202@\342-\343\\203\344,\3452;\203\364\332\3332#\202\374\334A@2\**\2028\342-\344\\203\312,\2028\342-\346\\203!\347,\312*\2028\342-\350\\2032\351,\312*\2028\312\211,*5.6b\210*\202\211 [org-called-with-limited-levels org-outline-regexp outline-regexp org-outline-regexp-bol parent prevs t org-get-limited-outline-regexp ^ outline-next-heading nil org-before-first-heading-p org-skip-whitespace line-beginning-position throw exit org-back-to-heading \n beginning-of-line org-element-headline-parser org-element--current-element element :parent org-add-props plist-put :end get-text-property 0 plist-get :contents-begin :contents-end (plain-list table) (center-block drawer dynamic-block inlinetask property-drawer quote-block special-block) (item plain-list) eql plain-list item :structure property-drawer node-property table table-row struct trail special-flag type end origin keep-trail value ...] 10) org-element-at-point() org-table-begin(any) org-at-table\.el-p() org-element-table-parser(23 (5)) org-element--current-element(23 element nil nil) byte-code(`\212\306\307 \211\310P\311 \210,`)\312\211\211\211\211\211\211 *+,-./\306\307 \211\310 P\313 \203Teb\210\314 \210m\204L\315 /V\203\205\316\317\312\\210\202\205\320 \210\312y\210\314 \210m\204i\315 /V\203\205\316\317\321\312x\210\322 \2100\204~\323d\306\\202\203\323d\306\C\\210,\322
Re: [O] help with MWE error: Variable binding depth exceeds max-specpdl-size
Hello, Titus von der Malsburg malsb...@posteo.de writes: I often get this error message after updating Emacs or org mode and forgetting to restart Emacs. Indeed, it looks like Myles English is using an outdated org-element.el library: org-element-at-point() org-table-begin(any) org-at-table\.el-p() org-element-table-parser(23 (5)) `org-element-table-parser' doesn't call `org-at-table.el-p' anymore since aa9c4bfb6fe1f5db240b4f9b2d781abd1138e018. Regards, -- Nicolas Goaziou
Re: [O] help with MWE error: Variable binding depth exceeds max-specpdl-size
I often get this error message after updating Emacs or org mode and forgetting to restart Emacs. Titus On 2015-07-03 Fri 10:12, Myles English wrote: Hello, Using the latest git HEAD (048f0), I am trying to make a MWE for another problem however, can someone please tell me what is missing from the init file because I get an error when I press TAB in the table. Starting emacs like this: $ emacs a.org -Q -l init.el with these files: a.org - * x | a | |---| | 1 | init.el --- (setq debug-on-error t) (add-to-list 'load-path ~/.emacs.d/plugins/org-mode/lisp) (add-to-list 'load-path ~/.emacs.d/plugins/org-mode/contrib/lisp t) (require 'org) ;;(require 'org-index) I get this traceback: Debugger entered--Lisp error: (error Variable binding depth exceeds max-specpdl-size) outline-on-heading-p(t) org-at-heading-p() org-element--current-element(23 element nil nil) byte-code(`\212\306\307 \211\310 P\311 \210,`)\312\211\211\211\211\211\211*+,-./\306\307 \211\310P\313 \203Teb\210\314 \210m\204L\315 /V\203\205\316\317\312\\210\202\205\320 \210\312y\210\314 \210m\204i\315 /V\203\205\316\317\321\312x\210\322 \2100\204~\323d\306\\202\203\323d\306\C\\210,\322 \210\324.\325,*$\211@-\326\f12\211;\203\263\327\31221$\202\304A\330A@21#\240\210+\2100\203\322+B+\3312;\203\351\332\3332#\202\361\334A@2\*\2113/W\204\f3/U\2053.U?\2053b)\204\211-4\204.\316\3170\203'+\202)\\210\202\211\3352;\203E\332\3332#\202M\334A@2\*\3362;\203e\332\3332#\202m\334A@2\*5\2116\203\2745\203\2746/V\204\2745/W\204\2746/U\203\232-\337\204\2745/U\203\317-\340\204\274-\341\203\3175b\210n\204\274m\204\317\316\3170\203\310+\202\312\\210\202@\342-\343\\203\344,\3452;\203\364\332\3332#\202\374\334A@2\**\2028\342-\344\\203\312,\2028\342-\346\\203!\347,\312*\2028\342-\350\\2032\351,\312*\2028\312\211,*5.6b\210*\202\211 [org-called-with-limited-levels org-outline-regexp outline-regexp org-outline-regexp-bol parent prevs t org-get-limited-outline-regexp ^ outline-next-heading nil org-before-first-heading-p org-skip-whitespace line-beginning-position throw exit org-back-to-heading \n beginning-of-line org-element-headline-parser org-element--current-element element :parent org-add-props plist-put :end get-text-property 0 plist-get :contents-begin :contents-end (plain-list table) (center-block drawer dynamic-block inlinetask property-drawer quote-block special-block) (item plain-list) eql plain-list item :structure property-drawer node-property table table-row struct trail special-flag type end origin keep-trail value ...] 10) org-element-at-point() org-table-begin(any) org-at-table\.el-p() org-element-table-parser(23 (5)) org-element--current-element(23 element nil nil) byte-code(`\212\306\307 \211\310 P\311 \210,`)\312\211\211\211\211\211\211*+,-./\306\307 \211\310P\313 \203Teb\210\314 \210m\204L\315 /V\203\205\316\317\312\\210\202\205\320 \210\312y\210\314 \210m\204i\315 /V\203\205\316\317\321\312x\210\322 \2100\204~\323d\306\\202\203\323d\306\C\\210,\322 \210\324.\325,*$\211@-\326\f12\211;\203\263\327\31221$\202\304A\330A@21#\240\210+\2100\203\322+B+\3312;\203\351\332\3332#\202\361\334A@2\*\2113/W\204\f3/U\2053.U?\2053b)\204\211-4\204.\316\3170\203'+\202)\\210\202\211\3352;\203E\332\3332#\202M\334A@2\*\3362;\203e\332\3332#\202m\334A@2\*5\2116\203\2745\203\2746/V\204\2745/W\204\2746/U\203\232-\337\204\2745/U\203\317-\340\204\274-\341\203\3175b\210n\204\274m\204\317\316\3170\203\310+\202\312\\210\202@\342-\343\\203\344,\3452;\203\364\332\3332#\202\374\334A@2\**\2028\342-\344\\203\312,\2028\342-\346\\203!\347,\312*\2028\342-\350\\2032\351,\312*\2028\312\211,*5.6b\210*\202\211 [org-called-with-limited-levels org-outline-regexp outline-regexp org-outline-regexp-bol parent prevs t org-get-limited-outline-regexp ^ outline-next-heading nil org-before-first-heading-p org-skip-whitespace line-beginning-position throw exit org-back-to-heading \n beginning-of-line org-element-headline-parser org-element--current-element element :parent org-add-props plist-put :end get-text-property 0 plist-get :contents-begin :contents-end (plain-list table) (center-block drawer dynamic-block inlinetask property-drawer quote-block special-block) (item plain-list) eql plain-list item :structure property-drawer node-property table table-row struct trail special-flag type end origin keep-trail value ...] 10) org-element-at-point() org-table-begin(any) org-at-table\.el-p() org-element-table-parser(23 (5)) org-element--current-element(23 element nil nil) byte-code(`\212\306\307 \211\310 P\311 \210,`)\312\211\211\211\211\211\211*+,-./\306\307 \211\310P\313 \203Teb\210\314 \210m\204L\315 /V\203\205\316\317\312\\210\202\205\320 \210\312y\210\314 \210m\204i\315 /V\203\205\316\317\321\312x\210\322 \2100\204~\323d\306\\202\203\323d\306\C\\210,\322
Re: [O] problem with ox-pandoc export
Richard Lawrence richard.lawre...@berkeley.edu writes: Rasmus ras...@gmx.us writes: I don't see it as reinventing the wheel. One example, does pandoc have something like the ox filters? It does; see e.g. http://pandoc.org/scripting.html Pandoc filters are actually more powerful than Org filters in most cases, because they are AST transformations. Pattern matching makes it convenient and practical in Haskell to just transform the part of the tree you're interested in. And because the Pandoc data structure has a JSON serialization format, filters can be written in just about any language, not just Haskell. This is an nice system, IMHO, which has one big advantage: it is possible to write complex filters (i.e., those that do more than just simple string manipulation) in an output-agnostic way. Pandoc filters can do things which are generally only possible or convenient to do in Org by creating a derived backend, which isn't output-agnostic. For the record, you can do the same in Org with a parse tree filter. Other filters are meant to be less powerful but easier to write. Regards,
[O] Structuring and (cross)linking information in org-mode
Hi all, I’m new to this mailing list and very eager to see what’s up in here. Is it still active? I hope so. Emacs is old, but it seems that still many people use it. So am I. After trying many different approaches to organizing information and tasks, I’m now looking into Emacs / org-mode, because I like the efficient keyboard-centric text-mode way of working. One question that I did not find a satisfactory answer for on my numerous days of research about Emacs / org-mode (however, maybe I „don’t see the wood for the trees“): I want to mix information and tasks in one file. That’s how it’s supposed to be, as far as I understand. I want to enter information as a journal, relatively strictly. So if I add a note to an appointment, I’d like to add that note not in the file area of that appointment, but to the end of the file, crosslinking the appointment and the new note. Is there a way to achieve that easily? I know how to make tasks with the org-todo-keywords. Now I want to mark chunks of information in that file in a similar way, but keep it outside of the task workflow. I’d like to have that information accessible and finable easily, and I want to differentiate different kinds of information. Quick example: * TODO This is my first task Some task description goes here * MEETINGNOTE of meeting 2015-07-02 MyCompany ** participants *** — John Doe *** — Mary Sample ** Goal This is the description of meeting goal ** Outcome Outcome of the meeting * PERSON John Doe Street address email address telephone * COMPANY MyCompany address field of operation employees: - John Doe - Mary Sample * INFO 2015-07-01 John Doe does not want to work with Emacs * NOTE 2015-07-02 16:20 called John on the phone here go some notes about the telephone call with John So for example: - I’d like to have all the info (cross)linked, so that if I click e.g. on any occurrence of „John Doe“ I’d like to see a list of matches that mention John Doe: his PERSON entry, the notes of meetings he participated, the company he is an employee of etc. How can I mark up info in a way that Emacs or org links such info? Or isn’t this possible? Do I have to use Gnowsys or something like that for this? - I’d like to be able to search all „PERSON“ entries for a specific name. - I’d like to be able to archive chunks of information, e.g. a MEETINGNOTE that’s obsolete, equally as I can do it with tasks - I’d like to filter, i.e. have Emacs only show me e.g. the „MEETINGNOTES“ entries with all their text, but filter out everything else. Maybe even only „MEETINGNOTES“ with tag „XY“… combined filtering. Possible via Agenda, as I understand it, at least partially. Matching tags and combinations of tags etc. Fot those of you who owned (or still own) a HP 200LX Palmtop and use Andreas Garzotto’s excellent PIM/PE on it (PE was a text editor that was partially inspired by Emacs and PIM was quite similar to org-mode, although PIM existed prior to org-mode): I’d like to do something similar with Emacs / org that was possible with PIM/PE. :-) Thanks for any hints, pointers and ideas, Daniel
[O] Extract document structure from Org file
Hello list! Suppose I wanted to extract the structure from an Org document, where, what's important for me would be to have it cathegorically divided into headers, paragraphs of text, technical information and inclusion of other documents (code snippets). How would I do it? The reason I'm asking is that I've a small project I work on, where I'm trying to enhance the search in documents by using indexing combined with queries based on things like distance between words, frequency of a word appearing in a document and so on. (I'm using Sphinx for it.) I've tried to do this with Info pages, and I liked the results, however, in order to do this more intelligently, I'd like to index the documents with better granularity (i.e. so that later on I could search assigning different weights to words appearing in headers and words appearing in comments). Best. Oleg
Re: [O] task b starts when task a is marked as DONE?
Nick Dokos ndo...@gmail.com writes: Sharon Kimble boudic...@skimble.plus.com writes: How can I have a task start when a primary task ends. I mean like this - * TODO task a - fill the rubbish bag * TODO task b - put rubbish bag into the bin outside. So in this case task b starts when task a is marked as DONE. Is it possible for this to occur please? what do you mean by start? Are you talking about clocking, about TODO states, about something else? When the TODO status changes to DONE, clocking can then autostart on task b. Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk TGmeds = http://www.tgmeds.org.uk Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.2 signature.asc Description: PGP signature
[O] Paste from clip/kill ring as cold block?
Hi list i use code block alot in my various org mode users. while the C-c C-v d is fast to use i find that alot of my use cases are focused on pasting stuff and then converting that into code blocks. i was wondering if anyone knew or uses his own mini script of a way to paste from the clipboard/killring as a code block? ie if i have XYZ in the clip it would paste as #+BEGIN_SRC emacs-lisp XYZ #+END_SRC maybe one could use hydra to choose which language to paste as code just an idea, would love to hear if anyone is using something similar best Z
Re: [O] Org-lint -- Lisp error: (wrong-type-argument arrayp nil)
Nicolas Goaziou writes: Fabrice Niessen writes: Same error with file https://github.com/fniessen/refcard-org-babel/blob/master/docs/eval.org. I cannot reproduce it. Could you pull again wip-lint and try one more time? Thank you. It works, indeed. Sorry. Though, there is one error with which I don't agree: --8---cut here---start-8--- 367 high Missing colon in header argument ) --8---cut here---end---8--- where line 367 is indicated by : --8---cut here---start-8--- #+name: add1 #+begin_src emacs-lisp :var x=1 :results silent (+ x 1) #+end_src #+call: add1(x=4) #+results: add1(x=4) : 5 #+call: add1(6) #+results: add1(6) : 7 #+call: add1(add1(9)) #+results: add1(add1(9)) : 11 --8---cut here---end---8--- Best regards, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] [BUG] org-clock-display is partial (only some entries are counted)
Hello Nicolas, Nicolas Goaziou writes: Sebastien Vauban writes: Applied the patch: [...] Tested on one of my real files, with: [...] Got this: Debugger entered--Lisp error: (error Specified time is not representable) [...] BTW, `untilnow' is not proposed when TAB'ing on `C-u C-u C-c C-x C-d'. Time for another take on this. What about the following patch? Perfect for me... I now have the expected total durations displayed. Best regards, Seb -- Sebastien Vauban
Re: [O] problem with ox-pandoc export
Rasmus ras...@gmx.us writes: And it is high quality exporter(s)? I don't know. However it doesn't matter much for formats we are not going to provide an export back-end anyway. Are there any exporters in particular that we need? rtf, rst, mediawiki might be useful. I think Bastien wanted to write ox-mediawiki.el at some point. I fail to see the logic here. There is none, but I needed one additional reason to convince myself I was right. Regards,
Re: [O] Org-lint -- Lisp error: (wrong-type-argument arrayp nil)
Fabrice Niessen fni-news-TA4HMoP+1wHrZ44/dzw...@public.gmane.org writes: Though, there is one error with which I don't agree: 367 high Missing colon in header argument ) where line 367 is indicated by : Are you sure you are using the latest wip-lint? It should be fixed already (commit 406cfbf2a148c4ea98278603ed5b096bbcdd5370, cherry-picked from master). Regards,
Re: [O] Maybe 1st ox-texinfo manual in the wild
Rasmus ras...@gmx.us writes: Hi, The magit 2.1 manual was typeset using ox-texinfo, it seems. Neat. Very cool! And this is a perfect opportunity to repost the link to Tom's org-manual-in-org, which I mostly keep around because it's a great example of how to do texinfo in the Org source. Good indexing is what keeps Info relevant! And what a relief to be able to do it in Org. https://raw.githubusercontent.com/tsdye/orgmanual/master/orgmanual.org
Re: [O] Extract document structure from Org file
Hi Oleg, Oleg Sivokon olegsivo...@gmail.com writes: Suppose I wanted to extract the structure from an Org document, where, what's important for me would be to have it cathegorically divided into headers, paragraphs of text, technical information and inclusion of other documents (code snippets). How would I do it? You would use org-element. Try org-element-parse-buffer and org-element-map and maybe org-element-interpret-data. There's also a bunch of regexp for identifying/finding particular types of elements. Cheers, Rasmus -- To err is human. To screw up 10⁶ times per second, you need a computer
[O] ELisp expression in a var not executed anymore on tangle
Hello,
I noticed that the following code block:
--8---cut here---start-8---
#+begin_src shell :tangle yes :var workingDir=(file-name-directory (or
load-file-name (buffer-file-name))) :shebang #!/bin/sh
cmd=$EMACS -q -l ${workingDir}init.el
#+end_src
--8---cut here---end---8---
does now return this:
--8---cut here---start-8---
#!/bin/sh
cmd=$EMACS -q -l ${workingDir}init.el
--8---cut here---end---8---
instead of:
--8---cut here---start-8---
#!/bin/sh
workingDir='d:/Users/sva/ecm/'
cmd=$EMACS -q -l ${workingDir}init.el
--8---cut here---end---8---
IIRC, you can also see that it's not working by pressing `C-c C-v C-v'
(preview).
Best regards,
Seb
--
Sebastien Vauban
