Bastien writes:
> Thorsten Jolitz writes:
>
>> ,-
>> | M-: (callOrgDisplay)
>> `-
>>
>> with point on the second level headline shows that internal string
>> representation. Only if I make `callOrgDisplay'
Bastien writes:
> Thorsten Jolitz writes:
>
>> both print this in the message buffer
>>
>> ,--
>> | byte-code: End of buffer
>> | #("1st level" 0 9 (face org-level-1))
>> `--
things don't work out of the box
right now, since I just started to code this today, but with time there
will be hacks and fixes that will enable more and more Org-functionality
in outshine buffers.
--
cheers,
Thorsten
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> How is this function supposed to be called from another program? Why
>> does it have (interactive "P") if the prefix arg is never used? Or do I
>> simply miss something important here?
>
> I th
g is never used? Or do I
simply miss something important here?
--
cheers,
Thorsten
ou are probably looking for something more sophisticated, but this
(untested) snippet should do the job when you are on a subheadline:
#+begin_src emacs-lisp
(save-excursion
(org-up-element)
(org-mark-subtree)))
#+end_src
--
cheers,
Thorsten
p in Org-Mode?
have a look here:
http://orgmode.org/manual/TODO-dependencies.html
--
cheers,
Thorsten
Hi List,
can inactive timestamps appear in
- title-stamps (the timestamps attached to headlines)
- planning types like deadline, scheduled and closed
?
It does not seem to make much sense to me, but maybe I'm overlooking
something.
--
cheers,
Thorsten
Or should it work even for bigger files and there must be an error on my
side (e.g. in loops/recursions)? I'm not sure how powerful Emacs is
w.r.t. this, i.e. how easy it is to bring it to the its limits with such
a hook that is triggered all the time.
--
cheers,
Thorsten
eractively 'org-version)
#+end_src
#+results:
: Org-mode version 8.2.5g (release_8.2.5g-564-ge45d13 @
/usr/share/emacs/24.3/lisp/org/lisp/)
instead of
#+begin_src emacs-lisp
(org-version)
#+end_src
#+results:
: 8.2.5g
--
cheers,
Thorsten
Nick Dokos writes:
> Thorsten Jolitz writes:
>
>>> > So if non-nil, it will be a list of tags, starting with the
>>> value of
>>> > org-archive-tag. AFAICT, the rest of the tags can be arbitrary.
>>>
>>>
Jonathan Leech-Pepin writes:
> Hello,
>
> On 4 March 2014 09:47, Thorsten Jolitz wrote:
>
>
> Nick Dokos writes:
>
> > Thorsten Jolitz writes:
> >
> >> Hi List,
> >>
> >> the name of head
Nick Dokos writes:
> Thorsten Jolitz writes:
>
>> Hi List,
>>
>> the name of headline attribute `archivedp' suggests its just a boolean
>> nil/t variable, but in parse trees I see e.g. a list as value
>>
>> ,--
Nick Dokos writes:
> Thorsten Jolitz writes:
>
>> Hi List,
>>
>> the name of headline attribute `archivedp' suggests its just a boolean
>> nil/t variable, but in parse trees I see e.g. a list as value
>>
>> ,--
ts value is "ARCHIVE"
`---
?
PS
If the tag is just a string like in this case, why is it shown as
list in the parse tree?
--
cheers,
Thorsten
n commented out (like Bastien and others). But
if the price for this would be Nicolas abandoning the parser/exporter
development I would say that this would be a VERY BAD DEAL for
Org-mode.
Just my 2c
--
cheers,
Thorsten
Nicolas Goaziou writes:
> Thorsten Jolitz writes:
>
>> This is the first code block of the original .org file with one link
>> (that could not be exported really, because it was evaluated on
>> another machine so the eps did not really exist on my machine. But the
>&g
Thorsten Jolitz writes:
> Vitalie Spinu writes:
>
>> Is there an easy way to copy org sub-tree in :filter-parse-tree?
>>
>> The structure of the parsed tree is somewhat complicated with recursive
>> references to parents in multiple places. So, copy-tree inflo
Nicolas Goaziou writes:
Hello,
> Thorsten Jolitz writes:
>
>> when trying to export this example lilypond file
>>
>> https://raw.github.com/mjago/ob-lilypond/master/examples/basic-mode/pdf-example/pdf-example.org
>>
>> to LaTeX (C-
yntax.
| CONTENTS is its contents, as a string or nil. INFO is ignored."
| (if (and contents (stringp contents) (> (length contents) 0))
| (format "%S"
| (org-no-properties contents))
| ""))
`----
--
cheers,
Thorsten
" \t"))
`-
link-end is nil but goto-char requires an integer-or-marker-p.
Not sure if there is wrong syntax in the file or if the parser is
confused by (correct) lilypond syntax.
PS
Org-mode version 8.2.5g (release_8.2.5g-564-ge45d13)
--
cheers,
Thorsten
\\
\cmidrule(lr){4-5}\cmidrule(lr){5-5} [linebreak]
\cmidrule(lr){6-6}\cmidrule(lr){7-7} [linebreak]
...
Thanks in advance!
Regards
Thorsten Grothe
nd the machine you use for shearing sheeps
will be a kind of smart-phone too that peeps if you need more than the
SCHEDULED time for one sheep, or the time for
,-
| "[#A] TODO Melk the Cows :farm:"
`-
has arrived ...
--
cheers,
Thorsten
ode]
\\
\cmidrule(lr){4-5}\cmidrule(lr){5-5} [linebreak]
\cmidrule(lr){6-6}\cmidrule(lr){7-7} [linebreak]
...
Thanks in advance!
Regards
Thorsten Grothe
from an external program (incorrect output with
strange underscore in the file where output was redirected)?
Any hints are welcome.
--
cheers,
Thorsten
Yasushi SHOJI writes:
> Hi,
>
> On Feb 15, 2014 11:38 PM, "Thorsten Jolitz" wrote:
>>
>> ,---
>> | (global-set-key (kbd "") 'org-agenda)
>> `---
>
>
plement my own
> function?
>
> Thanks in advance,
instead of:
,-
| (global-set-key "\C-ca" 'org-agenda)
`-
use:
,---
| (global-set-key (kbd "") 'org-agenda)
`---
--
cheers,
Thorsten
t...@tsdye.com (Thomas S. Dye) writes:
> Andreas Leha writes:
Hi all,
>> I guess you are looking for org-structure-template-alist
> This is from Bernt Hansen:
thanks, thats what I was looking for (and probably borrowed from Bernt
Hansen in my last setup)
--
cheers,
Thorsten
+begin_src instead of #+BEGIN_SRC etc.), and I even remember that I
had this configuration in the past, but I can't find the related
customizations anymore.
Any hints?
--
cheers,
Thorsten
)
#+end_src
the result looks fine, so it might be related to your config.
PS
#+BEGIN_SRC emacs-lisp
(message "%s" (org-version))
#+END_SRC
#+results:
: 8.2.5g
--
cheers,
Thorsten
"Sebastien Vauban"
writes:
> Thorsten Jolitz wrote:
>> Bastien writes:
>>> Thorsten Jolitz
>>> writes:
>>>
>>>> 3. can deadline and closed have repeaters?
>>>
>>> No.
>
> Not true for the first item: d
Thorsten Jolitz writes:
> Nicolas Richard writes:
>
> Hello,
>
>> I attach a patch which changs that and various other things related to
>> the renaming, namely : the customize interface, the README, and a change
>> in org-test (the one mentionned in <
f a library can have two (provide ...) statements, in that
case ob-shell.el could have simply used both of these:
,-
| (provide 'sh)
| (provide 'shell)
`-----
--
cheers,
Thorsten
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> 1. can deadlines be time-ranges?
>
> No.
>
>> 2. in time-ranges, can both entries have repeaters?
>
> No.
>
>> 3. can deadline and closed have repeaters?
>
> No.
>
>> 4. are
Bastien writes:
Hi Bastien ,
> Thorsten Jolitz writes:
>
>> Is there any restriction in the use of planning/time info other than
>> common sense? If so, what are the ruled-out combinations and attribute
>> assignments?
>
> Common sense applies, but it applies b
is a list of objects in the DB:
|
|
| *{
|-{{11}}
|-{{36}}
|-{{45}}
| }
`---
This might be contrived, but is actually not that exotic.
--
cheers,
Thorsten
bute
assignments?
--
cheers,
Thorsten
#C] My C Tasks
** Subtask
** Subtask
** Subtask
and let the textual order of the subtasks determine their priority:
most important on top, least important at the bottom.
Then insert a new task where you think it fits ...
> On 2014-01-30 16:51, Thorsten Jolitz wrote:
>> Fredrik writes:
&g
g below it?
Why not use ABC and differentiate with tags, e.g.:
* TODO [#C] Not important :low:
* TODO [#A] Really important
* TODO [#B] More important then kind of important
* TODO [#C] Kind of import :medium:
--
cheers,
Thorsten
ENT
keyword that is somehow a special case in the syntax.
--
cheers,
Thorsten
Thorsten Jolitz writes:
> Bastien writes:
>> I can't reproduce this, maybe you can bissect your config
>> and see what's wrong there?
>
> Ok, thanks, I did that and as I thought the problem was in my init file:
>
> ,---
Bastien writes:
> Hi Thorsten,
>
> Thorsten Jolitz writes:
>
>> I wonder why these variables, defined in org.el, are nil? I don't seem
>> to set them anywhere, and they should be defined once org.el is loaded,
>> shouldn't they?
>
> Not when O
Thorsten Jolitz writes:
PS
I forgot:
#+BEGIN_SRC emacs-lisp
(message "%s\n\nOrg: %s" (emacs-version) (org-version))
#+END_SRC
#+results:
: GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.6)
: of 2014-01-18 on mnt-storage-buildroots-staging-x86_64-eric
:
: O
--
I wonder why these variables, defined in org.el, are nil? I don't seem
to set them anywhere, and they should be defined once org.el is loaded,
shouldn't they?
--
cheers,
Thorsten
Nicolas Goaziou writes:
Hello,
> Thorsten Jolitz writes:
>
>> Your function could be implemented along the line of:
>>
>> 1. put an 'after' advice on `org-toggle-checkbox'
>
> See also `org-checkbox-statistics-hook'
>
>> Its easy
cs-lisp
(defun org-list-struct ()
"Return structure of list at point.
...)
#+end_src
but I could not find an equivalent function to get the item at
point.
--
cheers,
Thorsten
Bastien writes:
> Hi Thorsten,
>
> Thorsten Jolitz writes:
>
>> 2. M-: (org-timestamp-up 3)
>>
>> results in:
>>
>> ,--
>> | ** Cafe <2014-01-23 Do 19:35>
>> `--
>>
>
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> Bug or feature?
>>
>> Why is there this special handling of minutes? Evaluating
>>
>> ,-
>> | (org-timestamp-up 3)
>> `-
>>
>> with p
(> n 0) (- rem) (- dm rem))
[...]
)
#+end_src
--
cheers,
Thorsten
-
but the files have been renamed to ob-shell instead of ob-sh:
,
| -rw-r--r-- 1 tj users 9399 21. Jan 02:48 ob-shell.el
| -rw-r--r-- 1 tj users 9223 21. Jan 02:48 ob-shell.elc
`----
--
cheers,
Thorsten
d the
macro so that it automatically indents the code --> in Auctex this is
C-c C-q C-e ?
If not, no problem but I think this would be a nice feature :-)
Regards
Thorsten Grothe
Hi all,
this is my first post to this list, so please be patient with me :-)
I have many radio tables in my document with this structure:
\begin{comment}
#+TBLNAME: sec-10
#+ORGTBL: SEND sec-10 orgtbl-to-latex :skip 3 :splice t
|+---+---|
| Anscha
t know if this would work in Org-mode with re-exporting just like
in AucTex with re-compiling. But anyway, I guess you are looking for an
Emacs solution without external programs like Evince.
--
cheers,
Thorsten
Hi List,
when exporting an Org file, is the order in which things happen:
1. transcode all elements
2. filter all elements
or rather
1. transcode and filter one element
2. transcode and filter the next element
3. ...
?
--
cheers,
Thorsten
he first line
2. this is the second line with baz as the value
3. this is the third line
#+begin_src emacs-lisp :exports none :results raw
(org-export-as 'ascii)
#+end_src
#+results:
_
506
Thorsten Jolitz
Nicolas Goaziou writes:
> Hello,
>
> Thorsten Jolitz writes:
>
>> I wonder if customization options for the export of properties drawers
>> could be extended to something like this
[...]
> You can use a filter to do it, without needing to extend the variabl
t might be all the others
including those specified by users.
Furthermore, I would like to prefix properties, e.g.
* Header
:PROPERTIES:
:foo_prop1: bar1
:foo_prop2: bar2
:END:
and then be able to export all properties with a given prefix (matched
by a regexp like "foo_.+").
--
cheers,
Thorsten
Nicolas Goaziou writes:
Hello,
> Thorsten Jolitz writes:
>
>> Hi List,
>>
>> in ox.el I find this function for getting the (optional) alternative
>> title of a headline:
>>
>> #+begin_src emacs-lisp
>> (defun org-export-get-alt-title (headline i
:alt-title is nil? If the
application code needs a title string anyway, it can always fall-back to a
call to the get-title function.
--
cheers,
Thorsten
Nicolas Goaziou writes:
Hello,
> Thorsten Jolitz writes:
>
>> when writing an exporter backend, I wonder what is the canonical way to
>> extract the (optional) timestamp element from a headline's :title
>> attribute (which holds a secondary string)?
>>
&
-lisp
(let ((ttl (org-element-property :title headline)))
(and (> (length ttl) 1)
(car (last ttl
#+end_src
but I hope there is a more straight-forward and reliable way to do this?
--
cheers,
Thorsten
d before for me. Does it work for somebody
else?
--
cheers,
Thorsten
#+results: table-one
| a |
| b |
|---|
| c |
#+NAME: table-two
#+CALL: table-one[:hlines yes]()
#+results: table-two
| a |
| b |
| c |
but
#+begin_src emacs-lisp :var table=table-one :hlines yes
table
#+end_src
#+results:
| a |
| b |
|---|
| c |
seems to be a problem with #+CALL then ...
--
cheers,
Thorsten
---|
> | c |
>
>
> #+NAME: table-two
> #+CALL: table-one()
> #+RESULTS: table-two
> | a |
> | b |
> | c |
>
> #+NAME: table-three
> #+CALL: table-one[:results raw]()
> #+RESULTS: table-three
> : ((a) (b) hline (c))
>
> # --
--
cheers,
Thorsten
Matt Price writes:
> On Thu, Nov 7, 2013 at 4:37 PM, Thorsten Jolitz wrote:
>> Matt Price writes:
[...]
>>> I would like to keep the full tree visible in the navi-mode buffer
>>> while narrowing the original org buffer. I wonder if this is
>>> possi
ith only one
headline unfolded, while all navi searches still act on the whole file.
--
cheers,
Thorsten
Hello,
Nicolas Goaziou writes:
> Thorsten Jolitz writes:
>
>> But when I use something like this in the headline transcode function
>>
>> #+begin_src emacs-lisp
>> (format "(headline %S %s) "
>> [... return headline string ...]
>&
Hello,
Nicolas Goaziou writes:
> Thorsten Jolitz writes:
>
>> Aaron Ecay writes:
>>
>> Hi Aaron,
>>
>>> I would have expected multiple author lines to have this effect, so that
>>> your desired list of two authors would be generat
Aaron Ecay writes:
Hi Aaron,
> I would have expected multiple author lines to have this effect, so that
> your desired list of two authors would be generated by:
> ,
> | #+author: Thorsten Jolitz
> | #+author: Thomas Mueller
> `
>
> But it seems that only the la
re-installing, my outlines show all the stars, and the stars cannot be
> turned off. I've tried:
>
> #+STARTUP: indent
> #+STARTUP: hidestars
>
> Suggestions? Is there some sort of M-x hidestars command that I might
> have toggled accidentally?
What does 'C-h v org-startup-indented' show?
--
cheers,
Thorsten
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> I see (somehow random) underscores in html-exports, but no hint
>> whatsoever in the original Org file where they might come from.
>
> Are they really underscore or unbreakable spaces?
They might have st
er function, e.g.
#+begin_src emacs-lisp
(defun org-html-section (section contents info)
[...]
;; Build return value.
(format "\n%s"
class-num
(or (org-element-property :CUSTOM_ID parent) section-number)
contents)
#+end_src
but that looks to me just how I treated 'contents' above.
Any tips would be appreciated.
--
cheers,
Thorsten
to display
> your new text. I don't know if there's a way around this, and
> probably it would be better to use one of the existing outline modes
> for the guide window, but I don't know how to use those. Maybe
> Thorsten or someone can comment on how to improve that
Nicolas Goaziou writes:
> Hello,
>
> Thorsten Jolitz writes:
>
>> I wonder why the :author attribute in INFO is a list (while :email,
>> :creator and others are not)?
>
> :author's value is parsed, as all keywords in
> `org-element-document-properties'
Hi List,
I wonder why the :author attribute in INFO is a list (while :email,
:creator and others are not)?
It would make sense if several authors would be collected as a list of
strings, like e.g.
,-
| ("Thorsten Jolitz" "
r to the communication channel.
Thanks for the quick response! Helps me to avoid inventing some
workaround ...
--
cheers,
Thorsten
ID of the original parse-tree they belonged to,
and using the input-file (or input-buffer) name when creating this unique
ID seems only logical.
--
cheers,
Thorsten
http://www.gnu.org/software/emacs/manual/html_node/emacs/Mark-Ring.html#Mark-Ring
`--
--
cheers,
Thorsten
Aaron Ecay writes:
Hi Aaron,
> 2013ko azaroak 1an, Thorsten Jolitz-ek idatzi zuen:
>> I tested the above functions with a big org file - way to slow.
>> These versions perfom better, but only on property drawers:
>>
>> #+begin_src emacs-lisp
>> (defun org-s
Thorsten Jolitz writes:
> Matt Price writes:
>
>> Is there a command to fold all drawers in a buffer (all property
>> drawers would be enough, actually)? Or a suggestion for how to do
>> this? Thanks!
>
> They might exist (with me unaware of them), but the fol
min))
(while (not (eobp))
(and (org-at-drawer-p)
(not (org-element-property :hiddenp (org-element-at-point)))
(org-cycle))
(forward-char
#+end_src
#+results:
: org-hide-drawers
--
cheers,
Thorsten
e "Active modes are %s" active-modes)
| active-modes))
`---
--
cheers,
Thorsten
buffer)
(org-export-as 'html))
#+end_src
#+results:
ls
This also exports correctly
ls
This does NOT export correctly (code block is not detected)
#+BEGIN_SRC sh
ls
#+END_SRC
with html export, the last case does look quite different from the other ones.
--
cheers,
Thorsten
--
| #+results:
|_
|
| 427
|
| Thorsten Jolitz
|_
|
|
|
|
|
| 1 --text follows this line--
|
|
| Omid writes:
|
| > - This does
Nicolas Goaziou writes:
> Hello,
>
> Thorsten Jolitz writes:
>
>> with tmp.org
>>
>> #+begin_src org
>> * TODO [#A] This *is* _the_ \Headline\ <2013-10-13 So 04:44> :tag1:
>> :PROPERTIES:
>> :CUSTOM_ID: abc123
>> :END:
nt
#3))
#+end_src
Note that
#+begin_src emacs-lisp
(latex-fragment (:value \Headline :begin 17 :end
26 :post-blank 0 :parent #1))
#+end_src
should really be an =(italic (...))= object.
--
cheers,
Thorsten
Nicolas Richard writes:
> Also, I heard recently on #org-mode about bugpile, which is an old (last
> updated more than a year ago) of Thorsten Jolitz and Eric Schulte. The
> doc says:
This wasn't implemented, unfortunately, but stay tuned ... its somehow
still in the pipelin
eater-type cumulate :repeater-value
1 :repeater-unit month)))
#+end_src
It looks as if the combination of repeater *and* special warning period
prevents the parsing of both of them.
--
cheers,
Thorsten
,--
| ... and_they offer an ...
`--
and there seems to be nothing special between 'and' and 'they' in the
original text. Any ideas?
PS
I only noticed this when calling the exporter via emacsclient, not via
standalone emacs, but I possibly overlooked it before.
--
cheers,
Thorsten
:results raw
(let ((lst))
(org-map-entries
(lambda () (cons (org-entry-properties) lst))
"match" 'file))
#+end_src
#+results:
FILE . /home/tj/News/drafts/drafts/419) (TAGS . :match:) (ALLTAGS
. :match:) (BLOCKED . ) (ID . 3f78f08a-ccca-4fc0-aba9-2a192f7a0e5a) (foo . 5)
(bar . puppy) (CATEGORY . 419))) (((FILE . /home/tj/News/drafts/drafts/419)
(TAGS . :match:) (ALLTAGS . :match:) (BLOCKED . ) (ID .
3f78f08a-ccca-4fc0-aba9-2a192f7a0e5c) (foo . 7) (bar . hippie) (CATEGORY .
419
--
cheers,
Thorsten
the-property-API.html
`--
to read out the property values. Then do the calculation and finally add
a new property with the result.
--
cheers,
Thorsten
http://www.emacswiki.org/emacs/emacs-w3m][Emacs Wiki]].
PS
Here is the ChangeLog entry for the new emacs-w3m feature described above:
,-----
| 2013-10-07 Thorsten Jolitz
| * w3m-form.el (w3m-form-input-textarea-mode-setup):
ady transforms the plain text of
an org document into lisp (code = data), only that nobody has written
functions for the elements and objects yet, the parse-tree is just used
as data for the exporter.
* Footnotes
[fn:1] Those #1= and #1# are only print-syntax, otherwise they are references
to already defined elisp objects.
--
cheers,
Thorsten
here the macro seems to work.
Any idea what makes TAB work for Org-mode but not for Outshine on the
console?
--
cheers,
Thorsten
r attempt to 'do it right' based on a library by Francois
Pinard, [[https://github.com/tj64/org-weights][org-weights.el]], uses
overlays and dynamic updates of the tree-weights via change hooks - much
better in theory - but somehow overwhelms Emacs capacities in big files
so that user experience is affected.
--
cheers,
Thorsten
on-display-list 'frame-list
| 514:(defun gnus-get-buffer-window (buffer &optional frame)
| 527:;;; gnus-win.el ends here
`-
--
cheers,
Thorsten
Carsten Dominik writes:
> On 1.10.2013, at 19:50, Thorsten Jolitz wrote:
>
>>
>> Hi List,
>>
>> for the navi-mode keyword-search for complete property drawers I copied
>>
>> ,---
>> | org-property-drawer-re
>> `--
::END:
| 234::PROPERTIES:
|::CUSTOM_ID: OrgFileStructure
|::END:
`-
A bug in the regexp?
PS
Can anybody explain this marvelous construct in the regexp:
,-
| [^\\000]
`-
I often pondered about how to achieve its effect with other means, since
I did not find it in the Emacs Lisp manual.
--
cheers,
Thorsten
|::END:
`---
Although navigation inside the Org-modes buffers is quite convenient, its
somehow even more convenient to have a splitted screen and switch to the
read-only navi-buffer and use 1-key bindings for navigation, visibility
changes, all kinds of buffer views, and even a kind of remote control for
common copy, edit and search commands.
--
cheers,
Thorsten
Suvayu Ali writes:
> On Fri, Sep 27, 2013 at 11:29:57AM +0200, Thorsten Jolitz wrote:
>> Nicolas Goaziou writes:
>>
>> Hello,
>>
>> > Thorsten Jolitz writes:
>> >
>> >> although I did not update recently, html-export of this tes
501 - 600 of 961 matches
Mail list logo
