ou should already have Gnus. It comes with Emacs. Did you do something
to actively remove it?
—Rasmus
--
Enough with the bla bla!
r used el-get.
Hope it helps,
Rasmus
--
Summon the Mothership!
> e.g.
> asciidoc or markdown but keep the features?
No! BTW: Org already exports to md.
—Rasmus
--
Dung makes an excellent fertilizer
ly an ox-html
limitation? If the latter I could try to add it.
Thanks,
Rasmus
--
Hooray!
t.
Should I apply it, or is there a better way to fix this bug?
Thanks,
Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
>From 3f352159d9011e6a00af853fa6dadb04a5b46c87 Mon Sep 17 00:00:00 2001
From: rasmus
Date: Tue, 9 Dec 2014 12:40:52 +0100
Subject: [PATCH] ox.el
Rasmus writes:
> The attached patch fixes this by explicitly saving the footnote section
As per usual my first patch is dodgy. It occurred to me that Org can
handle several footnote sections (that's how #+INCLUDE supports footnotes,
I guess). The attached patch how supports export o
refer converting [fn:N] references to [fn::FOOTNOTE] (see my other
email). Any obvious downsides?
—Rasmus
--
Vote for proprietary math!
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Clearly the current situation is not satisfactory ("You can use :lines,
>> but only if no footnotes are present. . . IOW, :lines supports a subset
>> of Org syntax.").
>>
>> I prefer converting [fn
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>
>>> I think required definitions should be extracted from the included file
>>> and inserted at the end of the source file, without any footnote
>>> section.
>>
>> The
ed-4
Also, if you do not have FSF copyright papers sorted out you need to add
TINYCHANGE. See the same page.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
., Google Docs, Gmail, OSX Notes,
> etc.).
OK...
> Are there any options built in to org-mode that'd let me enable this?
No. And I doubt it should be. But Emacs is /your/ extensible editor.
—Rasmus
--
Need more coffee. . .
how to do it lisp look at how `org-edit-special', namely the keyword
part.
Hope it helps,
Rasmus
--
Send from my Emacs
Rainer M Krug writes:
> Is there an easy way of opening all INCLUDEd files in an org document,
> i.e. a single command or an easy way of doing it via some elisp code?
Oh, sorry, I didn't see the "all". But yeah, it should be easy with
org-element-map. Map over all keywords, ensure they are INC
t;> commit that introduced it was
>>
>>5633f7084a96298f415f07c348844bd5f22eb81e
>>
>> I didn't find a commit that deleted it but that's not surpising: it
>> probably went away when the new exporter came in.
>
> This is probably equivalent to `org-export-expand-include-keyword'.
This i
.org" :minlevel N+1
The easiest way I can think of would be to do a pre-scan of the
buffer to see if there exists any instances where include is only
separated by whitespace in which case they should have the same
level.
3. Fix the particular nastiness above by removing
rt the "{" characters?
I don't remember if this works in Org6 and it's not available to me.
Try:
#+LATEX: loop line 1
#+LATEX: loop line 2
#+LATEX: loop line 3
Or
#+begin_latex
My loop {}
#+end_latex
Let's hope one of those works in Org6.
—Rasmus
--
Vote for proprietary math!
d like
whatever
CSS adds a spurious space in front of my comma... Anybody feel strongly
in favor of keeping this newline? Or can I push this patch?
—Rasmus
--
C is for Cookie
>From c990d10b6a649e169ad6bfae61063b597d735771 Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Tue, 16
e this?
Thanks,
Rasmus
--
Together we will make the possible totay impossible!
test.org
Description: Lotus Organizer
minimal... Try the attached file which has a title. I definitely see
it here, zooming in and out, especially when the window ain't to large...
BTW: I tested using Firefox and Gnome Web.
> (As you can guess from my attitude, though, I'm not a professional web
> developer.)
As y
and a \vfill replacement for
print. And the above. Other than that I'm quite pleased with html.
—Rasmus
Footnotes:
¹ Here's what it looks like zooming in and out:
http://i.imgur.com/RLHI47C.png
--
Bang bang
g to the document order of the
> elements even as the script changes that order.
Interesting.
> To loop through them, try simply
>
> var e = elements[0]; // instead of var e = elements[i];
Thanks this is very helpful.
Next step: Proper small caps and make it work well on my phone!
T
(org-element-property
>> + :contents-begin definition)
>> + (org-element-property
>> + :contents-end definition)))
>>
Rasmus writes:
>> AFAICT, there's no reason to include a rule about whitespace separating
>> anything. Just make sure that any INCLUDE keyword that doesn't have
>> a :minlevel property gets one set to 1+N, where N is the current level
>> (or 0 if at top level)
o supply a patch to the manual check out this page:
http://orgmode.org/worg/org-contribute.html
You could submit a TINYPATCH.
God jul,
Rasmus
--
I feel emotional landscapes they puzzle me
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> I use CSS to make inlined lists in html:
>>
>> #text-sec ul {margin: 0; padding: 0; list-style: none;}
>> #text-sec li {display: inline;}
>> #text-sec li:after {content: ", &qu
uot;correctly" in
getting the "right" level. But it probably does not matter for export.
See this test for my initial reasoning:
(should
(org-test-with-temp-text
(format "* h1\n#+INCLUDE: \"%s/examples/include.org::#ah\""
org-test-dir)
(org-na
s to Org
> documents. WDYT?
That's a nice solution. Implemented in attached patch.
Should this be added to ORG-NEWS? Is a "feature" or a "bug-fix"?
Thanks,
Rasmus
--
Vote for proprietary math!
>From 1fa88054255e66922ea9e2cd61310461901ac6ee Mon Sep 17 00:00:00
ence in a wide buffer. If you're not within narrowed
> boundaries stored before, put it in the hash table. Otherwise, skip it.
> It doesn't require `org-element-context' or `line-number-at-pos'.
OK. I do it in a differently now, relying on org-footnote-get-definition.
Or do
e preserved", or
something like that...
> All code blocks sharing the same name are exectuted by the same interpreter
> process. By default, a session is not started.
—Rasmus
--
Dobbelt-A
e)))
>> + (when label
>> +(let ((new-label
>> + (buffer-substring-no-properties
>> +(point)
>> +(progn (if digit-label (insert (format "fn:%d-" id))
>> +
x27;t survive a M-q.
Let's M-q it then.
>> +(goto-char (1+ (org-element-property :begin reference)))
>> +(when label
>
> Shouldn't these two lines be inverted?
Sure that's prettier.
Cheers,
Rasmus
--
ツ
>From 2382ee420c97a801560dff3e9
Hi,
Nicolas Goaziou writes:
> Rasmus writes:
>
>>>> * Foo
>>>> [1] foo
>>>>
>>>> * Bar
>>>> Baz[1]
>>>
>>> I'm not sure to understand. Would you mind elaborating?
>>
>> If I have #+INCLUDE: &qu
file?
I'm probably misunderstanding, but how about just adding a time stamp on a
note in one of your agenda files? E.g.:
** My Trip Home
<2014-12-24 07:12-14:55>
Hope it helps,
Rasmus
--
If you can mix business and politics wonderful things can happen!
complete is obsolete:
(unless (or org-completion-use-ido org-completion-use-iswitchb)
(setq org-completion-use-iswitchb t))
You could also update the docstring of `org-completion-use-iswitchb'.
See http://orgmode.org/worg/org-contribute.html for the details.
Cheers,
Rasmus
--
How
rt.
You could use snippets, but it's a bit inconvenient:
| d@@latex:[1]@@ |
You could make macro that inserts a snippet for whichever backend is the
current one
#+MACRO: num (eval (format "@@%s:[%d]@@" org-export-current-backend $1))
| d{{{num(1)}}} |
(Only tested with latex).
just saw).
Please let me know if I did any git mistakes. Somehow the time got skewed
up and it's behind some of your commits in cgit. . .
Cheers,
Rasmus
--
May the Force be with you
.org::#ah\""
org-test-dir)
(narrow-to-region (point) (point-max))
(org-export-expand-include-keyword)
(eq 1 (org-current-level
If somebody knows *why* this I would appreciate an explanation. (Can
anybody confirm the above on their system?)
Thanks,
Rasmus
--
. . . It begins of course with The Internet. A Net of Peers
Hi,
Rasmus writes:
> Please let me know if I did any git mistakes. Somehow the time got skewed
> up and it's behind some of your commits in cgit. . .
Hmm, inspecting cgit I see that one of those persky merge messages got up
there even though it wasn't in my local git lo
"it's nil"
=> (1 . "it's nil")
But now I updated and indeed it returns (1 . 1).
—Rasmus
--
Tack, ni svenska vakttorn. Med plutonium tvingar vi dansken på knä!
ng like the attached patch, "make test" goes from
passing to failing with a fresh Org. Why is it 1 when evaluated from a
text-file?. Or perhaps the Magic Pixies are just angry with me. . .
—Rasmus
PS: I'll fix the test and push it.
--
Not everything that goes around comes back aro
he functions lacking a docstring in org-macs.el.
Org-folks are generally generous in reviewing patches and the tone is
friendly.
Cheers,
Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
Karl Voit writes:
> I do not use any Google service at all besides Google search
> which is giving me better search results than DuchDuckGo -
> unfortunately.
Did you try startpage.com? It can also be searched directly from DDG, I think.
—Rasmus
--
With monopolies the cake is a lie!
ent: ", ";}
#text-my-sec li:last-child:after {content: "";}
I don't know what bootstrap is though, so I don't know if it helps.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
to reproduce on my system:
>> CLOCK: [2015-01-03 Sat 21:20]--[2015-01-03 Sat 21:21] => 0:01
>> * TODO =bar=
I wonder if we could use a arrow character or similar for "=>". It would
probably be a "can of worms".
—Rasmus
--
A page of history is worth a volume of logic
Hi,
RC writes:
> If the default heading and content classes used by ox-html could be
> changed or aliased it should work well with org-mode html
Maybe you can set up filters then to replace e.g. section into the desired
naming-scheme. AFAIR class-names are hard-coded in ox-html.
—
e can fix it would be
great; otherwise input on whether this is truly the place to fix this
behavior please let me know.
Thanks,
Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
┃ ┃ 8:00-14:50 Drink coffee
┃ ┃
[icon] ┃15:30-15:45 Catch bus
For a more "blocky" view as found on e.g. the ASOP Calendar, I think Calfw
is the right tool. I don't remember if it has any support for vertical
control of entries.
—Rasmus
--
Hvor meget poesi tror De kommer ud af et glas isvand?
Peter Davis writes:
> Is there any way to completely redact text in HTML export, so it just
> looks like black boxes?
I'm not sure I fully understand, but it this what you are looking for?
#+MACRO: redact @@html:$1@@
to {{{redact(redact)}}} or not to {{{redact(redact)}}} that is the question.
cted to
> #+ATTR_ODT: :style TableWithHeaderRowAndColumn
Fixed.
Thanks for reporting!
BTW: The former syntax was changed quite a while back.
Thanks,
Rasmus
--
Dung makes an excellent fertilizer
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Ah, it's much easier to use \stopcontents[level-i] to end contents
>> collection. Revising the example:
>>
>> \documentclass{book}
>> \usepackage{titletoc}
>> \begin{doc
lly".
>
> I don't mind updating the footnote relative to titletoc package in the
> manual. Do you want to provide a patch?
I can add documentation, but please reconfirm that you find the above
limitations acceptable and want to see suggestions of modifying
org-latex-packages-alist in the manual!
—Rasmus
--
m-mm-mmm- bacon!
Hi Seb,
Sebastien Vauban
writes:
> - baz ::
>
> generates the error "replace-regexp-in-string: Wrong type argument:
> arrayp, nil".
This has been fixed.
I forgot to acknowledge that you reported the bug. Sorry!!
I can revert the commit and redo the commit if you think?
Sebastien Vauban
writes:
> What counts is that *you* *fixed* it!
I also introduced it cf. the log!
--
. . . It begins of course with The Internet. A Net of Peers
pos (not titletocp))
(push '("" "titletoc" nil)
(nthcdr pos org-latex-default-packages-alist)
Cheers,
Rasmus
--
. . . The proofs are technical in nature and provides no real
understanding
Nicolas Goaziou writes:
> Rasmus writes:
>
>> As said, I'd prefer load hyperref via org-latex-hyperref-template, but
>> it's probably too big a change too late. Though, it would resolve the
>> "issue" that if I do
>>
>>(s
lter to insert "\clearpage" at
the end on headlines with the appropriate property or tag. A quick hack:
(defun rasmus/get-org-headline-string-element (headline backend info)
"Return the org element representation of an element.
Won't work on ~verb~/=code=-only headers"
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I was putting this to further support another solution, namely moving
>> hyperref to a single defcustom, allowing hyperref to be inserted after all
>> other header-lines.
>
> As you pointed out already, moving hyperre
5 to 10, 10 excluded}
@end example
Is there any logic behind when @r{·} and when (·) is used? Or should we
try to make it more coherent?
Thanks,
Rasmus
--
This is the kind of tedious nonsense up with which I will not put
Nicolas Goaziou writes:
>> Or should we try to make it more coherent?
>
> IMO @r{.} should be used everywhere in these situations.
I pushed a commit that removs the ()-comments I could find.
—Rasmus
--
m-mm-mmm- bacon!
-parse-buffer). Well simply because I don't need everything. in
> first implementation I only need:
> OR HEADLINE under point and it's subtree
> (HEADLINE (plainlist (item,item,item)),(subheadline),...)
> OR the headline of an ITEM under point and subtree
> (headline (plainlist (item, ITEM,item)),(subheadline),...).
So use org-element-map and org-element-parse-buffer.
Hope it helps,
Rasmus
--
The second rule of Fight Club is: You do not talk about Fight Club
Hi Dieter,
Dieter Van Eessen writes:
> Hello Rasmus,
>
> Thank you for the fast reply, the link you've given on interpreting is very
> useful ! Also didn't know there existed such thing as the org-dp library to
> manipulate org-elements, I'll sure check it out.
I
Hi,
davi...@es.gnu.org (David Arroyo Menéndez) writes:
> How can I do a org-todo-recursive? The idea is replace TODO by DONE in
> a tree. Someone with a snippet?
Does org-depend.el do what you need? [Your message is not very clear]
Cheers,
Rasmus
--
Governments should be afraid of
of org-depend.el, but from my point of view, org-depend
> is for triggers, I want make a request to a full subtree in org, not triggers.
Can you give a simple example of what you have got in mind? Do you want
to change the TODO-state of all subheadings relative to the current heading?
—Rasmus
--
Summon the Mothership!
n your init.el? If so that's the issue.
Otherwise, nothing looks suspicious in the log and I can't reproduce the
issue with the current head.
Cheers,
Rasmus
--
When the facts change, I change my mind. What do you do, sir?
dlines (the syntax is
unfortunate, especially for people who write Org without org-mode).
Thus, I like Aaron patch, though we could add a defcustom if it breaks
somebody's setup.
Cheers & Thanks,
Rasmus
--
The right to be left alone is a human right
2. or (org-agenda nil "t")
Hope it helps,
Rasmus
--
This space is left intentionally blank
tr)
(org-trim (match-string 1 str
#+END_SRC
#+RESULTS:
: baz qux
There's a similar "parser" in org-export-expand-include-keyword. If you
know which argument you are looking for you can replace the \\w+ above.
Hope it helps,
Rasmus
--
Send from my Emacs
s indeed interpret
correctly as a latex-fragment. Yet, the nested environment is recognized
as a latex-environment and it seems the former can't "hold" the latter.
Why the above work is because a latex-environment starts on its own line
(cf. org-element--latex-begin-environment).
Nicolas w
t goal 1 & 2 come out in an enumeration.
You haven't by chance customized org-export-headline-levels? Or set H:n
(n is a number) in your #+OPTIONS-line? Try to set n to something like 3.
Cheers,
Rasmus
--
ツ
other symbol) vs \checkmark.
I would like to remove at least sup from org-entities.el, but I'm biased.
This breaks compatibility, so we should thread carefully here. Any
thoughts?
Cheers,
Rasmus
--
This is the kind of tedious nonsense up with which I will not put
e to synchronise contacts
>> stored in Org with arbitrary CardDAV servers.
Cool stuff!
Cheers,
Rasmus
--
With monopolies the cake is a lie!
Gour writes:
> On Sri, 2015-01-21 at 11:24 +0100, Rasmus wrote:
>
>> I use this as well. I don't know of a good step from owncloud-contancts
>> to Emacs (BBDB or Org, I don't care).
>
> How do you feed Gnus with your contact's email addresses when compos
or this kind of testing.
On the other hand, I'm happy that you (also) find joy in the Org format!
Cheers,
Rasmus
--
. . . It begins of course with The Internet. A Net of Peers
Hi,
Marcin Borkowski writes:
> Now Rasmus comes and says:
>
>> I must admit that I feel uncomfortable because you use the name
>> org-mode to promote a product that does not respect the "4 freedoms"
>> as put forth by the FSF. E.g. if you make mistakes, it m
:post identity(*this*)
setNames(data.frame(1:2), "foo")
#+END_SRC
#+RESULTS:
| 1 |
| 2 |
Expected result:
| foo |
|-|
| 1 |
| 2 |
--8<---cut here---end--->8---
Thanks,
Rasmus
--
However beautiful the theory, you should occasionally look at the evidence
Aaron Ecay writes:
> Hi Rasmus,
>
> You also have to add :colnames to the :post header:
>
> :post identity[:colnames yes](*this*)
Thanks Aaron. That even makes sense in its own, quirky way!
Should add a note on this to the manual? Or is it clear enough as it is?
—Rasm
Hi,
Aaron Ecay writes:
> 2015ko urtarrilak 25an, Rasmus-ek idatzi zuen:
>> Should add a note on this to the manual? Or is it clear enough as it
>> is?
>
> I think it would be a good idea to add a note about this in the manual.
> Perhaps in the form of another example i
Hi Sébastien,
Sébastien Brisard writes:
> my blog (sbrisard.github.io) is entirely written with
> org-mode.
Looks pretty.
> Org-mode offers everything I need, except for one minor
> detail. It is very difficult to include the same CSS file in the
> html-head of several files located at variou
uirements), plus everyone
and their mother's have got custom citation links in their config via
custom org link types...
/Proper/ citation support (not links) is, IMO, the last thing that is
missing for good academic publishing support.
#+end_rant
—Rasmus
--
I hear there's rumors on the, uh, Internets. . .
Matt Price writes:
> On Tue, Jan 27, 2015 at 8:30 AM, Rasmus wrote:
>> #+begin_rant
>>
>> The current state is a mess and not portable. E.g. there's at least two
>> Zotero projects, there's John Kitchin's code, there's ox-bibtex.el (which
Takaaki Ishikawa writes:
> Second, We have several workshops
> related to Emacs and org-mode. At least, two workshops are held a few
> times a year at Kyoto and Tokyo.
That's pretty cool. Thanks for sharing.
—Rasmus
--
This is the kind of tedious nonsense up with which I will not put
Hi,
Richard Lawrence writes:
> Rasmus writes:
>
>> IMO we /need/ to add proper citation support to Org, preferably with a
>> real syntax rather than these link-"solutions" and with good backend
>> support (bibtex & Zotero for starters, I guess).
>>
Hi,
Christian Moe writes:
>> Blah blah [see @doe99, pp. 33-35; also @smith04, ch. 1].
>
> In my current homebrewn solution for Zotero, I have tried to do
> something similarly readable using Org link syntax (sorry, Rasmus!) with
> the database entry ID as link targe
nts link and label.
The patch fixes this by only counting the length of the label.
I'm not really familiar with the ascii backend, so let me know if there's
any obvious deficits that I have overlooked.
Otherwise I push it.
—Rasmus
--
Evidence suggests Snow
begin 461 :at-heading t)
(:begin 493 :at-heading nil))
#+END_SRC
src_emacs-lisp{"not in headline"}
* src_emacs-lisp{"in head line"}
src_emacs-lisp{"not in headline"}
--8<---cut here---end--->8---
Hope it helps,
Rasmus
--
Governments should be afraid of their people
if it is common to have such long tags in description
> lists.
I don't know. If it is, maybe someone will complain.
—Rasmus
--
Me gusta la noche, me gustas tú
t; introducing citation syntax to Org should be compiling a list of all the
> things such a syntax should represent.
I think allowing for arbitrary keys is abstract enough to solve all
issues. It would also be easy to add user-written support.
> The other problems, I think, must wait until a stable citation syntax
> emerges -- export support in particular.
+1.
—Rasmus
--
It was you, Jezebel, it was you
n odt. Put it's a hard problem
'cause there's nothing quite like bib(la)tex (to the best of my
knowledge).
> I have also been working on a proposal for citation syntax that I think
> will meet these requirements, which I will post separately.
Cool! Let me know if I can help.
I have mainly worked on regexps for the syntax I proposed in another email.
—Rasmus
--
The second rule of Fight Club is: You do not talk about Fight Club
quot;breaks" whenever you have pre and post notes. Author-Year is pretty
common and pre and post is pretty damn important. Readability is
important and links fail at this step for any citation but the most simple
ones.
Links are "hard" to type outside of Emacs and logically/syntax-wise
unpleasant and are displayed poorly within Emacs.
—Rasmus
--
The second rule of Fight Club is: You do not talk about Fight Club
d also need to support custom display functions. You could then
implement a cite-operator '@' as a handler for a generalized link.
—Rasmus
--
Governments should be afraid of their people
Hi,
Richard Lawrence writes:
> Hi Rasmus and all,
>
> Rasmus writes:
>
>> Richard Lawrence writes:
>
>>> Within a citation, each reference to an individual work needs to be
>>> capable of containing:
>>> 1) a database key that references t
tation-key is defined in document use it. Otherwise check
BIBLIOGRAPHY_FILES.
> In the last example, the leading "*" is meant to indicate that the
> reference database is a subtree with headline "Reference DB", whose
> branches are in org-bibtex format.
Too much micromanagement. I prefer how footnote-definition works.
> ** Bibliography placement
> The simplest solution seems to be just allowing the #+BIBLIOGRAPHY
> keyword to appear anywhere in the document, to be replaced on export
> with the formatted bibliography. I think this is what ox-bibtex now
> does.
#+TOC works the same way.
—Rasmus
--
C is for Cookie
for other backends. I only use bibtex and I used
to separate pre/post with ";" so there's some legacy code in there.
Everything is hard-coded to my system/taste, written quickly and (very)
lightly tested, but maybe it will still be useful to somebody. . .
—Rasmus
(with-eval-af
Richard Lawrence writes:
> Hi Rasmus and all,
>
> Thanks for your comments!
>
> Rasmus writes:
>>> #+BEGIN_QUOTE
>>> [See @Doe99, pp. 34--45; also @Doe00:year, section 6]
>>>
>>> [See their article in @Doe99:journal:year.]
>>> #+END_
t prefer DOI.
If you can live with \cite-only there's already ox-bibtex.el that will
support bibtex citations in html.
—Rasmus
--
May contains speling mistake
Nicolas Goaziou writes:
q
> Hello,
>
> Bastien writes:
>
>>> Though, I think I have to withdraw my proposal about using #+DATE:
>>> value
>>> as a time format string. Indeed, date value, along with any
>>> document
>>> property, is parsed, which defeats the purpose of using it as a
>>> format
>>>
long time.
Perhaps we should set up a Worg TODO page for documentation? To make
it easier to contribute bits.
Thanks,
Rasmus
--
Vote for proprietary math!
ppropriate
white space (e.g. X + N).
What might be useful would be a tag telling Org to use the legacy
exporter on a file basis, although it would also be a short run
solution.
–Rasmus
--
Summon the Mothership!
h is shipped
with beamer.
Cool with the #+BEAMER. I didn't know about this, but it's super
nice. The other day I was lookking for a replacement to
#+BEAMER_HEADER (I think that was what it was called), which existed
with the 'old' exporter. Does this variable exist in Beamer yet
ld be sorted out on the LaTeX side,
e.g. via beamerarticle.
–Rasmus
--
Vote for proprietary math!
301 - 400 of 2037 matches
Mail list logo
