> challenge for pdf export, for example. The hook should run after the
> latex export, not after the pdf is made.
I don't think your example warrant an extra hook. Replacing strings is
something that org-export-filter-final-output-functions is perfectly
capable of doing IMO. It’
John Kitchin writes:
> Rasmus writes:
>
>> John Kitchin writes:
>>
>>> Hi all,
>>>
>>> I tried using org-export-before-parsing-hook to modify an org-file prior
>>> to export to replace some regular expressions with html.
>>&
ol-check-filename-for-protocol uri (list uri)
> nil
> + (should (equal (car org-stored-links) '("URL3" "TITLE3"
I don't know org-protocol well enough to comment on your tests. But I
guess you should add something like this, extrapolating from other test
files,
(unless (featurep 'org-protocol)
(signal 'missing-test-dependency "org-protocol"))
Cheers,
Rasmus
--
⠠⠵
ox-whatsoever-files I failed to find ox-latex ... so I think I'm
> thinking wrong ... :-(
>
> Can anyone help me out here?
It sounds like you don't have a recent version of Org. Please see the
installation instructions in the manual,
http://orgmode.org/org.html
Hope it helps,
Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
s.tex:
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[style=authoryear]{biblatex}
\addbibresource{cited.bib}
\begin{document}
\nocite{*}
\printbibliography[heading=none]
\end{document}
Rasmus
--
May contains speling mistake
might also serve as a warning.
Note, I use a similar system myself when exporting citations outside of
latex (lookup stuff from bibtex and cross-fingers), but fitted to
author-year. It’s certainly doable when you know your fixed needs, but it
is harder to convince yourself it’s a good general solution.
It would be nice if you could prove me wrong.
Rasmus
--
What will be next?
s Org.
> So what is the best export format from org for bitbucket READMEs? At the
> moment I am using text (UTF8) Which works, but I would like to have
> syntax highlighting and clickable links?
Probably Rst or markdown...
Rasmus
--
A clever person solves a problem. A wise person avoids it
produce pdf of commit)
- better web interface.
- git annex support
- you can install it on your own server when you no longer feel
comfortable with the gitlab.com installation.
Rasmus
--
Enough with the bla bla!
xx@@
Another hackish solutions would be to use a filter + footnotes with a
recognizable pattern, but I’m not sure I would go that way...
I doubt this help, but those were my 2 cents.
Rasmus
--
However beautiful the theory, you should occasionally look at the evidence
gn documents.
>
> WDYT?
I'd be happy to kill [n] style footnotes. I've had issues with them in
the past.
Rasmus
--
Not everything that goes around comes back around, you know
nd_center
Hope it helps,
Rasmus
--
What will be next?
is on a document level.
Or whether it is sufficient to document how users can change
org-export-smart-quotes-alist to their liking. The latter should be
sufficient (assuming an author has one strictly preferred style), but
reproducibility of Org document speaks in favor of a document setting.
Rasmus
--
Sådan en god dansk lagereddike kan man slet ikke bruge mere
York Zhao writes:
> Let's say I have two letters:
>
> * Letter1
> ** Preamble :noexport:
>
> #+DATE: 2015-10-26 Monday
> ** To whom it may concern,
>
>
> * Letter2
> ** Preamble :noexport:
>
> #+DATE: 2015-12-03 Thursday
> ** Hi,
This should work:
* letter 1
:PROPERTIES:
:EXPORT
n emacs package providing read/write
> access to this metadata ?
You could probably use exiftool with org-babel or dynamic blocks to
extract the required data and generated the syntax you want.
Hope it helps,
Rasmus
--
ツ
Hope this was what you were after.
Rasmus
--
Together we will make the possible totay impossible!
t; (org-combine-plists
> (list :src (gs/b64-img source) ; <-- interesting line is here
The comment is no good.
>:alt (if (string-match-p "^ltxpng/" source)
> (org-html-encode-plain-text
> (org-find-text-property-i
is inside a block? I’m trying to
write a function for structures (e.g. #+begin_latex) that works like
org-babel-demarcate-block.
Thanks,
Rasmus
#+BEGIN_LaTeX
|
#+END_LaTeX
#+BEGIN_SRC emacs-lisp
|
#+END_SRC
#+begin_abstract
|
#+end_abstract
--
Dung makes an excellent fertilizer
el-demarcate-block.
>
> (org-element-lineage (org-element-at-point) '(special-block) t)
That's very cool. Thanks.
Rasmus
--
Even a three-legged dog has three good legs to lose
> Secondly, even though it still produced a PDF output, the date is always
> today's date which is wrong.
I cannot reproduce. I get this as part of exporting the first subtree
(I click: C-c C-e C-s k L)
\date{2015-10-26 Monday}
Hope it helps,
Rasmus
--
Enough with the bla bla!
y:
https://github.com/mathjax/MathJax/issues
Thanks,
Rasmus
--
Dung makes an excellent fertilizer
Hi Dominik,
Thanks for investigating this further.
Dominik Schrempf writes:
> thanks for your answer. I asked the people from MathJax and the problem
> is HTML related. =
> This behavior is well known and explained in the MathJax
> Documentation.
>
> http://docs.mathjax.org/en/latest/tex.html#
letter.
#+options: title:nil
Or replace "letter 1" with the actual title or subject of the letter (see
org-koma-letter-prefer-subject for the latter).
Rasmus
--
Er du tosset for noge' lårt!
ind.
> The closest I've got was `org-koma-letter-subject-format', which can be
> set with "#+OPTIONS subject". But it seems that the "subject" option
> works the same as the "title" option, and has exactly the same problem.
I don't unde
ind this in INFO? Has this been documented
> there?
Yes. See here:
http://orgmode.org/org.html#Export-settings
Rasmus
--
I feel emotional landscapes they puzzle me
e desired style with
(Footnote-set-style 'unicode). We can eventually add keybindings for
footnote-mode in norgstruct that resemble Org, if necessary.
Rasmus
--
I feel emotional landscapes they puzzle me
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Can I now write:
>>
>> X[fn:1]
>>
>> [1] foot
>
> Uh? No.
> [...]
Very good! Thanks for clarifying.
Rasmus
--
A page of history is worth a volume of logic
Hi,
Nicolas Goaziou writes:
Thanks for the work.
> The following function, included in ORG-NEWS, updates any Org document
> to the new syntax. It is meant to be applied after applying the patch.
Will org-lint be able to detect and repair documents automatically?
Rasmus
--
Spil nog
such, the best outcome would be if Vaidheeswaran/Jamuthuan would
maintain it in "lisp". My understanding is that there is no issues on the
FSF/copyright side. I don’t know what the opinion of the Org developers
are, though.
In this case, moving ox-freemind to GELPA might be the path of least
resistance. As such, it seems like a good solution.
Rasmus
--
Er du tosset for noge' lårt!
ut it does not seem to change anything (I have tried to add bullet and
> stuff like that).
I think bullets are in orgstruct mode, but they could be in
orgstuct++-mode. BTW: there's also orgtbl-mode.
Rasmus
--
I almost cut my hair, it happened just the other day
t work from a clean Emacs? And a dirty?
(let ((org-html-postamble nil))
(require 'ox)
(with-temp-buffer
(insert "x")
(org-html-export-as-html)))
Rasmus
--
Nothing's wrong with an email that ends in a minor key
g automatically)? Is it worth breaking old documents
(irrespective of org-lint) for this inconvenience?
Rasmus
--
One thing that is clear: it's all down hill from here
display table being created for
them when org-mode is run. Unfortunately, I don’t know anything about
display tables.
Rasmus
--
C is for Cookie
ion (what if it’s not in
PATH) and whether section.lco is available via something like kpsewhich.
Note that e.g. TL also looks in the current path.
Regards,
Rasmus
--
Summon the Mothership!
s packaged as distro package, but I can survive
> some manual work.
This is because sections.lco is not part of KOMA-Script (like titlepage¹).
E.g. on my system with TL:
$ kpsewhich sections.lco
/home/rasmus/.texmf/tex/latex/koma-script/sections.lco
kpsewhich/tex also looks in the current
; +(mapcar 'list files) nil t)))
> + (path (expand-file-name file attach-dir)))
> +(if (and (file-symlink-p path)
> + (org-attach-use-annex)
> + (not (file-exists-p (file-symlink-p path
Can you ask annex if it's an annexed file? A symlink in an annexed
folder,
to a usb disk that is not attached would pass this test. But the
indication would be wrong.
> +(call-process "git" nil nil nil "annex" "get" path))
> +(org-open-file path in-emacs)))
Thanks,
Rasmus
Hi Kyle,
Kyle Meyer writes:
> Rasmus writes:
>
> [...]
>
>>> This patch automatically calls =git annex get PATH= when you open the
>>> attachment from Org, if the file has not been fetched already.
>>
>> This is a good idea. Though really this sound
psewhich are unknown to me, as
> I said I try to stay away from latex and tex as much as possible. If
> there is some agreement on the patch I will update the doc to add those
> info.
I think it’s best to add a switch (defcustom) either per document or at
least a global variable. It defaul
Kyle Meyer writes:
> Rasmus writes:
>
>>>> Has Joey spoken for or against automatic fetching of content when
>>>> requested?
>>>
>>> I think I'm missing something. Why would he have an issue with running
>>> "git annex get"
rn at the
> prompt ?
Here's naive approach. Probably you can find a more elegant way.
(condition-case nil
(while t
(call-interactively 'org-set-property))
(quit nil))
Rasmus
--
Spil noget med Slayer!
roperty unless you have good reasons not to (IMO). If you are working on
a hack do whatever you want...
Rasmus
--
Together we'll stand, divided we'll fall
Julien Cubizolles writes:
> Rasmus writes:
>
>
>> Does this do what you want:
>>
>> (call-interactively 'org-set-property)
>
> Thanks, indeed it does, Marcin beat you to it though :-)
>
>>> Also, I will sometimes need to include several
Ken Mankoff writes:
> On 2016-01-05 at 18:29, Rasmus wrote:
>> Ken Mankoff writes:
>>> I'm trying to figure out when I should be using tags and when I
>
>>> should be using properties, for the cases of "noexport" and
>>> "ignoringheadi
Julien Cubizolles writes:
> Rasmus writes:
>
>
>> For more fine grained control you probably need to write something akin to
>> org-set-property and check the actual values (e.g. to signal quit if an
>> empty quote is returned).
>
> Actually, shouldn't org
re not largefiles are checked in as normal git files.
Example:
$ git annex find .fonts/FiraMono-BoldItalic.ttf
.fonts/FiraMono-BoldItalic.ttf
# → checked in in annex.
$ git annex find .emacs.d/init.el
$ git log -n1 --oneline -- .emacs.d/init.el
9a8fd3a git-annex in W530: conf.annex
# → checked in in vanilla git.
Rasmus
--
This message is brought to you by the department of redundant departments
Marcin Borkowski writes:
> Hi all,
>
> and thanks in advance;-)!
Maybe something like this?
(defun rasmus/org-clock-in (&optional DEFAULT-BUFFER NEW-NODES NO-EXCLUDE)
"Clock in remotely"
(interactive)
(save-excursion
(goto-char (nth 3 (
ting the noeval header).
I think you should be queried from "emacs -q". If this is the case, it’s
probably some setting, e.g. in your init.el.
Hope it helps,
Rasmus
--
Got mashed potatoes. Ain't got no T-Bone. No T-Bone
e external files, you can #+include (e.g. #+include:
"file::*heading" ) them multiple times. Since you cannot include from the
same document as the include keyword is in you’d need at least two files.
Rasmus
--
Evidence suggests Snowden used a powerful tool called monospaced fonts
a physical letter or an email requesting to get the
form? If the latter, I think you can ping them again. Though, it was
just holiday, so they might have a backtrack.
Rasmus
--
Lasciate ogni speranza, voi che leggete questo.
could just check the log directly for failures rather than
checking the file attributes, if these are not reliable.
Also, what is the ‘take‘? I don’t seem to have it in my Emacs...
Rasmus
--
Even a three-legged dog has three good legs to lose
Peter Davis writes:
> Have I missed something?
Must it be a table? If not you might have missed the subcaption package.
http://thread.gmane.org/gmane.emacs.orgmode/92820
Rasmus
--
Need more coffee. . .
1 @@latex:}@@
#+attr_latex: :booktabs nil
| | |
| {{{imgtop([[file:img1.png]])}}} | {{{imgtop([[file:img2.png]])}}} |
Hope it helps,
Rasmus
Footnotes:
¹ See:
http://tex.stackexchange.com/questions/23521/tabular-vertical-alignment-to-top
--
May contains speling mistake
Rasmus writes:
> It is a solution to the problem:
>
>Place multiple images on one way the Correct Wayᵀᴹ when using ox-latex.
^^^
line
Typo.
--
Look, it is what it is because of what it was
Hi Anthony and Nicolas,
Anthony Cowley writes:
> Thanks for taking a look, Rasmus! The bug is in Org, not Emacs. One
> may perhaps assume the invariant that successive calls to
> `current-time` will return non-decreasing values. One might also
> assume the invariant that successiv
eplace lines?
Maybe CalDav? There's a tool on F-droid called Tasks (or maybe Task) that
can sync via DAVDroid to REPO.. Maybe org-caldav.el could be extended to
support the sync. tasks between Org and REPO.
Rasmus
--
C is for Cookie
Cloud v8.1.3.
(with-eval-after-load 'org-caldav
(setq org-caldav-url
"https://ras...@domain.net/owncloud/remote.php/caldav/calendars/rasmus";
org-caldav-calendar-id "defaultcalendar"
org-caldav-inbox "~/documents/cal/inbox.org"
org-caldav-
DULED” or “CLOSED”. TIMESTAMP is a
timestamp object.
In particular, no blank line is allowed between PLANNING and HEADLINE.
Rasmus
Footnotes:
¹ http://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning
--
Look, it is what it is because of what it was
er, a docstring.
Exceptions exists of course, e.g. when commands to repair files are
suggested.
Rasmus
--
This message is brought to you by the department of redundant departments
Hi,
Alan Schmitt writes:
> On 2016-01-18 12:28, Rasmus writes:
>
>>>> I almost forgot: would you mind preparing an entry about it for
>>>> ORG-NEWS?
>>>
>>> Is this too detailed?
>>
>> IMO Yes. As I recall the examples are also in th
Alan Schmitt writes:
> On 2016-01-18 15:21, Rasmus writes:
>
>>> Excellent point, how about:
>>>
>>> *** Attributes support in custom language environments for LaTeX export
>>> Custom language environments for LaTeX export
>>> (~org-latex-cus
phillip.l...@russet.org.uk (Phillip Lord) writes:
> Rasmus writes:
>
>> Hi Phillip,
>>
>> Thanks for your report.
>>
>> phillip.l...@russet.org.uk (Phillip Lord) writes:
>>
>>> On emacs-25 ox-html, line 1847, org-html-fontify-cod
; never ask me google incredients, so it seems to me a bug.
No idea.
>> (with-eval-after-load 'org-caldav
>> (setq org-caldav-url
>> "https://ras...@domain.net/owncloud/remote.php/caldav/calendars/rasmus";
>> org-caldav-calendar-id &quo
fy-buffer. In this particular case, using
> font-lock-ensure instead of font-lock-fontify-buffer fails to
> highlight the source block.
Cool!
Cheers,
Rasmus
--
May contains speling mistake
e
>> variant that avoids these issues, so I will do that (in an updated
>> patch and on Org's maint).
>
> I've attached updated patches against emacs-25. If these are applied to
> the Emacs repo, I'll backport the new font-lock-ensure alias to Org's
> maint.
Looks good, thanks.
Rasmus
--
Er du tosset for noge' lårt!
m, I
> really would like to use org-cdlatex-mode under Org-mode. Thanks in
> advance!
You can download it here:
https://raw.githubusercontent.com/cdominik/cdlatex/master/cdlatex.el
Add it to your load path.
Hope it helps,
Rasmus
--
There are known knowns; there are things we know that we know
10/emacs-org-cdlatex-mode-where-do-you-put-the-cdlatex-el-script
I did not check this.
Hope it helps,
Rasmus
--
The right to be left alone is a human right
back-ends accordingly, or should I?
My life is a bit stressful at the moment (deadlines). I'm happy to do it,
and maybe I can do it in the weekend, but if you feel like taking doing it
I won’t stand in your way.
Rasmus
--
The right to be left alone is a human right
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> What's wrong with equation (potentially coupled with mathtools for
>> handling numbering automatically)? Is it worth breaking old documents
>> (irrespective of org-lint) for this inconvenience?
>
>
t;annex" "add" new-or-modified)
> +(call-process "git" nil nil nil "add" new-or-modified))
In git annex v6 you don’t need to call "git annex add" (but can). In git
annex v5 you don’t need to call "git add".
To be compatible bet
dvantage that
> it would make it clear that any hanging is from the 'git annex get'
> call.
How about a defcustom that default to y-or-n-p? I think one should be
able to turn it off an on...
Rasmus
--
History is what should never happen again
t; all with org-attach?
Don’t know. I use org-attach. My dir is in a direct repo. It never
complained. Maybe there’s something I haven’t configured. Maybe it’s
cause I use the assistant. Don’t know...
> I’m happy to make that change, but I feel it should be a separate patch.
Indeed.
Thanks for working on this.
Rasmus
--
Got mashed potatoes. Ain't got no T-Bone. No T-Bone
g it
>> I won’t stand in your way.
>
> Just a friendly bump to make sure this doesn't get lost. I think the
> LaTeX patches should still apply; let me know if there's an issue
> tracker I could use to record the need for adjustments to other
> back-ends.
Short weeke
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Short weekend... Thanks for reminding. Would you be interested in
>> providing patches for the other backends? I’d be a bit troubled by fixing
>> a general issue for one backend only.
>
> FWIW, I applied the pa
s usually
something akin to an address field on the right side of the head. I think
"location" should be settable via a special :location: heading, probably
with special line breaking rules like the :to:/:from: special headings.
We can allow a #+LOCATION keyword in addition, but need not. All IMO.
WDYT?
Thanks,
Rasmus
--
This message is brought to you by the department of redundant departments
Hi Erik,
Thanks for the updated patch!
A couple of more comments follow.
I hope I’m not being too annoying!
Erik Hetzner writes:
> +(defcustom org-attach-annex-confirm-get-function #'y-or-n-p
> + "Function to call to confirm if Org should call git annex get if necessary.
> +If t, always get,
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Thanks! I have added a TODO to my agenda regarding checking other
>> backends, but I'd not hold grudges against anyone who beats me to it.
>
> I took care of ox-groff, ox-man and ox-texinfo.
Thanks.
>
> ** Change of address
>
> *** Location field:location:
> \usekomavar{frombank}
But is it much neater than:
** bank details :location:
Acc. no.: 12345
Big Bank Corp
Sort code: 1122
For temporary data, I’d rather have it like in my example. For permanent
data I can keep it in a .lco file.
And maybe #+include: "bank-info.org".
Thanks,
Rasmus
--
History is what should never happen again
left, I’d rather type:
* bank details :location:
Acc. No.: 1234567890
at Big Bank
Sort Code: 11-22-33
Than
#+latex_header: \setkomavar{frombank}{\raggedright
Acc.~No.:\,1234567890\\at Big Bank\\Sort Code: 11-22-33}
#+Location: \usekomavar{frombank}
To me the former reads much easier and hides away the technical details.
Thus, I wish to see to see support for entry forms.
Rasmus
--
The Kids call him Billy the Saint
this weekend. Again, unless someone
beats me to it.
> Alright, I get the general idea but in that specific case this would be
> simpler:
>
> #+LOCATION: \raggedright Acc.~No.:\,1234567890\\at Big Bank\\Sort Code:
> 11-22-33
You are right.
Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
(setq face-ignored-fonts '("Latin Modern Math"))
Hope it helps,
Rasmus
--
When in doubt, do it!
t’s lacking for the purpose of "tufing" ox-latex output?
In any I’m very happy that you are working on this. I hope the
above is not discouraging; that’s at least not what it’s meant to
be.
Thanks,
Rasmus
--
Vote for Dick Taid in an election near you!
interest though...
I don’t understand the difference between margin notes and
sidenotes from a 10 seconds skim.
Thanks,
Rasmus
--
You people at the NSA are becoming my new best friends!
Marcin Borkowski writes:
On 2016-02-03, at 12:05, Rasmus wrote:
Marginnotes. I don’t think we have a concept like this. I
guess
Inline todos?
It's not really the same. Inline todos are for temporary notes
(say bugs in your document) that you’d not want to keep in your
|
Hawai`i.;-3\baselineskip]]
`-
As you might’ve guessed, I’m not a fan of this solution. Whether
it’s numbered or not in the output, a [mn:N] or [sn:N] reference
is more Orgish. I cannot, however, speak to how difficult it
would be to add more note types.
Rasmus
--
Sådan en god
Hi Erik and Kyle,
Sorry for the delay, I was traveling this week. I’m happy with
the patch now and it has been pushed to master.
Thanks!
Rasmus
--
Don't slow down Johnny, leave the Cadillac runnin'
c KEYWORD (jk-org-kwds))) ""))
Hope it helps even if I’m unable to give an definite answer
regarding your second observation.
Rasmus
--
Need more coffee. . .
ch of
org-mode.git, which is targeting Emacs 24.3 or 24.4, you
might as well use cl-lib, the replacement of cl.
Hope it helps,
Rasmus
--
It was you, Jezebel, it was you
Hi Julien,
Julien Cubizolles writes:
I noticed that org-latex-compiler-file-string mentions an
"Indented LaTeX compiler". I guess it should be "Intended LaTeX
compiler".
Thank you for pointing this out! It’s fixed now.
Rasmus
--
Need more coffee. . .
news
;-)
It's also mentioned here, though it may be a unfair
characterization of org-dp:
http://emacs.stackexchange.com/a/2885/1974
Rasmus
--
Er du tosset for noge' lårt!
narrowed) buffer and has all context
info, and mostly is not used to write Org syntax (but rather
those of the export backends).
I edited it with (almost) the suggested quote, and added a pointer
back to your post here. I don’t know how much advertisement it
generates, though.
Rasmus
--
⠠⠵
;s it. Here’s a
recent example:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=aee808987da50fbf44fb762519914ae6bd458876
Cheers,
Rasmus
--
A clever person solves a problem. A wise person avoids it
bidi
package provides bidiftnxtra package that solves the issue of
footnote in standard LaTeX.
Rasmus
Footnotes: ¹
http://tex.stackexchange.com/questions/1583/footnotes-in-tables ²
http://ftp.snt.utwente.nl/pub/software/tex/macros/xetex/latex/bidi/bidi.pdf
--
Warning: Everything
mation is actually used. Should I use other
functions instead?
I’d say "no". I rely on plenty of hacks in my own documents (13
filters in my standard Makefile conf.el). There's nothing wrong
with that as long as you know that you are playing with the fire.
In this case you ne
AB as field separator
>
> ;;;
>
> Thus docu should mention the comma as possible separator.
Isn't it covered by the following line?
regexp When a regular expression, use it to match the separator
Thanks,
Rasmus
--
⠠⠵
vantage that it doesn't require another dependency.
For that reason I have a slight preference for resizebox (though I'd
probably use neither).
Thanks,
Rasmus
--
Nothing's wrong with an email that ends in a minor key
Myles English writes:
> Rasmus writes:
>
>> I will try to merge your patch soon, this weekend. Again, unless someone
>> beats me to it.
>
> Please would someone apply this patch?
I will *try* to write the remaining code to maintain feature parity
between keywords and
tomrule
\end{tabular}
\end{center}
Notes
\end{table}
You might have to tweak the centering to your liking (e.g. another center
special block and the attribute :center nil).
Hope it helps,
Rasmus
--
Evidence suggests Snowden used a powerful tool called monospaced fonts
> \author[1]{Author Four}
> \author[1]{Author Fourrr}
> \author[2]{Author Fou}
> \author[2]{Author Twenty}
> \affil[1]{Guided Therapeutics Centre}
> \affil[2]{Division of theatre}
> #+END_LATEX
If you insist on this you could use a filter.
Hope it helps,
Rasmus
--
When in doubt, do it!
7;ve asked this question
> before but can't find the answer...
Would this do what you want?
(save-excursion
(org-back-to-heading)
(org-element-at-point))
If you have a more sophisticated parse tree you could use
org-element-lineage.
Rasmus
--
Don't slow down Johnny, leave the Cadillac runnin'
like to have my specific "note" listed in the agenda, but
> what I need to do is so minor that I don't want it to have a "headline"
> in my notes. Is this possible?
AFAIK no.
You can have a task with check boxes: - [ ].
Rasmus
--
Vote for Dick Taid in an election near you!
>>> behaviour as before?
>>>
>>
>> I bet :wrap HTMP produces
>>
>> #+BEGIN_HTML
>> ...
>> #+END_HTML
>>
>> instead of
>>
>> #+BEGIN_EXPORT HTML
>> #+END_EXPORT
>
> So I guess the OP should write :wrap export HTML.
801 - 900 of 2037 matches
Mail list logo
