Charles Berry writes:
> Rainer M Krug krugs.de> writes:
>
>>
>> Sebastien Vauban
>> writes:
>>
>> > Rainer M Krug wrote:
>> >> Charles Berry writes:
>> >>> Rainer M Krug krugs.de> writes:
>>
>> when exporting the fillowing org file, I get an endless loop of
>> evaluations.
>
John Kitchin writes:
> Why cannot there be a list of acceptable keywords eg
>
> [citenum:
> [citeyear:
> [citeauthor:
>
> which a backend would be responsible for handling, including a default
> handler for unknown keywords?
It has the same problem as [pre @key post] syntax: it is slower to
pars
t...@tsdye.com (Thomas S. Dye) writes:
> Yes, I typically use what I call a multicite to get multiple citations
> with biblatex. It just inserts {key}. I precede two or more of these
> with a placeholder--π for parencites, † for textcites, or ƒ for
> footcites--and then use a filter to insert \p
Rasmus writes:
> Not necessarily. I could do:
>
>(defun rasmus/gentive-citation (citation-element backend)
> (case backend ...) ...)
>
>(add-to-list 'org-cite-types 'rasmus/gentive-citation )
>
> E.g. for genitive citations such as "Smith's (1984) model", which can be
> mostly
Hi
Following a recent discussion (based on me forgetting a ":" when setting
the property :header-args), I added the output of the property
header-args to the output of org-babel-get-src-block-info to make
debugging easier. Before the function resulted in the following output
(using my faulty code
Nicolas Goaziou writes:
> Another option is to mimic custom links, if that's what you're thinking
> of, which means to store every user-defined keyword in a variable and
> build a regexp out of it. I dislike it even more because the document is
> not portable anymore, as it requires you to share
Nicolas Goaziou writes:
> If you write something like
>
> [cite: pre1 @k1 post1; pre2 @k2 post2]
>
> wouldn't it possible to guess you want to use multicite? IOW, does using
> "multicite" really implies a change in the syntax?
To fully support multicite you need keyless citations in the beginn
Rasmus writes:
> Nicolas Goaziou writes:
>
>> If you write something like
>>
>> [cite: pre1 @k1 post1; pre2 @k2 post2]
>>
>> wouldn't it possible to guess you want to use multicite? IOW, does using
>> "multicite" really implies a change in the syntax?
>
> To fully support multicite you need ke
On Monday, 9 Feb 2015 at 21:59, deadbrain wrote:
> Hi all org-mode gurus,
> I am trying to generate a deck of slides using Emacs/org-mode /beamer &
> some companion tools (graphviz & plantuml).
> I have a problem to set the dimensions for the graphviz (or plantuml)
> generated pictures.
> Whatever
Nicolas Goaziou writes:
> I think
>
> [cite: common pre; pre1 @k1 post1; pre2 @k2 post2; common post]
>
> is regular and readable enough. So, there's no need to add special
> support for multicite.
Definitely.
In latex you'd just use multicite whenever more than two keys within one
cite-group
Rasmus writes:
> So, the (opinionated) useful defaults in biblatex are:
> cite(s), parencite(s), footcite(s), texcite(s), fullcite,
> footfullcite, nocite
Isn't footcite/footfullcite a choice made at the document's level
instead of per citation? If that's the case, it could go in a keywo
Thanks a lot Eric
The small sise was just there for my experiments to ensure my attributes
were processed
Thanks again i will be able to finish my deck of slides.
I did not know this syntax but I guessed that the workflow was the problem
Kind regards
Le 10 févr. 2015 10:51, "Eric S Fraga" a écrit
Nicolas Goaziou writes:
>> So, the (opinionated) useful defaults in biblatex are:
>> cite(s), parencite(s), footcite(s), texcite(s), fullcite,
>> footfullcite, nocite
>
> Isn't footcite/footfullcite a choice made at the document's level
> instead of per citation? If that's the case, it co
Hi,
Nicolas Goaziou writes:
> Rasmus writes:
>
>> So, the (opinionated) useful defaults in biblatex are:
>> cite(s), parencite(s), footcite(s), texcite(s), fullcite,
>> footfullcite, nocite
>
> Isn't footcite/footfullcite a choice made at the document's level
> instead of per citation? I
Hi
--8<---cut here---start->8---
#+PROPERTY: header-args :tangle-mode (identity #o444)
* Initial plottings
#+begin_src R
plot(1)
#+end_src
--8<---cut here---end--->8---
When calling org-babel-view-src-block-info (C-c C-v C
The attached file, when exported to ODT fails to open in LibreOffice
exporter. The reason failure is that the exported __XML__ file has
"nested footnote definiton" i.e., a footnote definition within a
footnote definiton. In concrete terms, there is some confusion wrt
the return value of `org-ex
Hi,
Cdlatex environment inserted via org-cdlatex-environment-indent are pretty
bad at getting the right indention. Consider:
- concept :: a long description of concept |
Where | is cursor. When I call org-cdlatex-environment-indent, I expect
- concept :: a long description of concept
Rainer M Krug writes:
> #+PROPERTY: header-args :tangle-mode (identity #o444)
>
> * Initial plottings
> #+begin_src R
> plot(1)
> #+end_src
>
> When calling org-babel-view-src-block-info (C-c C-v C-i) on the code
> block above, I get the error below.
>
> I don't have the slightest clue what this
Rasmus writes:
> Rainer M Krug writes:
>
>> #+PROPERTY: header-args :tangle-mode (identity #o444)
>>
>> * Initial plottings
>> #+begin_src R
>> plot(1)
>> #+end_src
>>
>> When calling org-babel-view-src-block-info (C-c C-v C-i) on the code
>> block above, I get the error below.
>>
>> I don't ha
Rasmus writes:
> Hi,
>
> Cdlatex environment inserted via org-cdlatex-environment-indent are pretty
> bad at getting the right indention. Consider:
>
> - concept :: a long description of concept |
>
> Where | is cursor. When I call org-cdlatex-environment-indent, I expect
>
> - concept
Hi,
Thanks for this. You have
[fn:1] footdef1[fn:2]
[fn:2] footdef2
What do you expect to see in ODT? Presumably not a footnote in a
footnote, since LibreOffice doesn't allow you to place one.
An ODT cross-reference to the footnote? That makes sense, but should
that be achieved by footnot
Subhan Michael Tindall writes:
> This is probably overkill, but I use this:
> (setq org-agenda-custom-commands (quote (
> ("c" "Clock" ((agenda ""
> ((org-agenda-sticky nil)
>
> (org-agen
Marcin Borkowski writes:
> On 2015-02-09, at 18:43, Paul Rudin wrote:
>
>> If I type "C-c a L" I get a list of durations for each day - for example:
>>
>> Monday 9 February 2015 W07
>> Clocked: (0:53) Revise document X
>> Clocked: (1:12) Meet Fred
>> ...
>
> Wow. I don't get this
I just found the following function:
,
| C-c C-v C-c runs the command org-babel-check-src-block, which is an
| interactive autoloaded compiled Lisp function in `ob-core.el'.
|
| It is bound to C-c C-v c, C-c C-v C-c.
|
| (org-babel-check-src-block)
|
| Check for misspelled header arguments
Update:
The problem occurs whenever a property value is a number.
so
,
| #+PROPERTY: header-args :tangle-mode 292
`
also produces the error.
Fix included in other patch.
Rainer
Rainer M Krug writes:
> Rasmus writes:
>
>> Rainer M Krug writes:
>>
>>> #+PROPERTY: header-args :ta
When I call either active or inactive timestamps and enter the current
date from the keyboard, i.e. 2/10, rather than simply pressing enter the
result is <2016-02-10 Wed> or [2016-02-10 Wed], i.e. the year is already
advanced. If I enter any date in the rest of the month in same manner
such as
Please find attached the below described patch including the fix for the
error reported - function raises error when property value is numeric.
Cheers,
Rainer
diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index ceda1aa..aa39c11 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -409,12 +409,
On Tuesday 10 February 2015 06:26 PM, Christian Moe wrote:
Thanks for this. You have
[fn:1] footdef1[fn:2]
[fn:2] footdef2
What do you expect to see in ODT? Presumably not a footnote in a
footnote, since LibreOffice doesn't allow you to place one.
An ODT cross-reference to the footnote?
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Another option is to mimic custom links, if that's what you're thinking
>> of, which means to store every user-defined keyword in a variable and
>> build a regexp out of it. I dislike it even more because the document is
>> not portable anymore, as i
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Yes, I typically use what I call a multicite to get multiple citations
>> with biblatex. It just inserts {key}. I precede two or more of these
>> with a placeholder--π for parencites, † for textcites, or ƒ for
>> footcites--a
I am trying to put a second row of two columns in a org beamer slide.
No problems with doing the first row, two column.
I can't figure out any way to put in the second row of two columns.
(I am trying to show a 2x2 grid of images, with titles.)
It appears to me I need something that produces and
John Kitchin writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>>
>>> Another option is to mimic custom links, if that's what you're thinking
>>> of, which means to store every user-defined keyword in a variable and
>>> build a regexp out of it. I dislike it even more because the document is
Hello,
does anyone use YASnippet with Org? I tried, but ran into a strange
problem: when I type into a placeholder field, I get a space after each
letter. Did anyone run into this, too?
TIA,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer
Hi Nicolas and all,
Nicolas Goaziou writes:
> If year, or author, are needed, I suggested to append some optional
> parameter to the key, e.g.,
>
> [cite: pre @key:year post]
I proposed exactly this earlier in the thread, but then I came to the
conclusion that we shouldn't do it.
Conceptuall
>
> Ok, sorry I didn't check the natbib manual carefully. AFAIK you get
> numbers with biblatex without any author-year options so:
>
> \cite{k}, \parencite{k} → [Num]
> \textcite{k} → A [Num]
>
> Is this similar to \numcite? From natbib is seems to be intended for
> people who use author-year,
Rasmus writes:
> So, the (opinionated) useful defaults in biblatex are:
> cite(s), parencite(s), footcite(s), texcite(s), fullcite,
> footfullcite, nocite
So that is to say we need to be able to express the following
distinctions (did I miss anything?):
- in-text vs. parenthetical (par
Hello,
Charles Millar writes:
> When I call either active or inactive timestamps and enter the current
> date from the keyboard, i.e. 2/10, rather than simply pressing enter
> the result is <2016-02-10 Wed> or [2016-02-10 Wed], i.e. the year is
> already advanced. If I enter any date in the rest
Richard Lawrence writes:
> Rasmus writes:
>> Citation types for extracting parts:
>> citeauthor, citetitle, citeyear, citedate, citeurl,
> As I've said in other posts, I think maybe we should not think of
> these as `citation' commands and thus don't need to represent them
> in citation s
I'd like a copy of the documentation (short, long manuals) in their
original .org format. Where can I find them? My first logical guess was to
get the org distribution. But /doc/ doesn't seem to have them as .org files.
LB
Lawrence Bottorff writes:
> I'd like a copy of the documentation (short, long manuals) in their
> original .org format. Where can I find them? My first logical guess was to
> get the org distribution. But /doc/ doesn't seem to have them as .org files.
It's in texi. E.g. doc/org.texi. There's a
What would the github link be?
On Tue, Feb 10, 2015 at 12:06 PM, Rasmus wrote:
> Lawrence Bottorff writes:
>
> > I'd like a copy of the documentation (short, long manuals) in their
> > original .org format. Where can I find them? My first logical guess was
> to
> > get the org distribution. But
Lawrence Bottorff writes:
> What would the github link be?
https://github.com/tsdye/orgmanual
Tom frequents the list regularly if you want to know more about it.
—Rasmus
--
Evidence suggests Snowden used a powerful tool called monospaced fonts
On Tue, 10 Feb 2015, Rainer M Krug wrote:
Hi
Following a recent discussion (based on me forgetting a ":" when setting
the property :header-args), I added the output of the property
header-args to the output of org-babel-get-src-block-info to make
debugging easier.
[snip]
Using the patched ve
On Tuesday, 10 Feb 2015 at 15:42, Larrabee Strow wrote:
> I am trying to put a second row of two columns in a org beamer slide.
>
> No problems with doing the first row, two column.
>
> I can't figure out any way to put in the second row of two columns.
> (I am trying to show a 2x2 grid of images,
Hi,
Thanks for the suggestion.
I tried making the columns bigger "BEAMER_col: 0.8 or whatever
Didn't work.
I tried making the image bigger (but maybe org doesn't see that)
I don't have any other ideas on how to do this. Maybe because I have no
text in the slide?
Larrabee
--
"Charles C. Berry" writes:
> On Tue, 10 Feb 2015, Rainer M Krug wrote:
>
>> Hi
>>
>> Following a recent discussion (based on me forgetting a ":" when setting
>> the property :header-args), I added the output of the property
>> header-args to the output of org-babel-get-src-block-info to make
>> d
Hello,
Christian Moe writes:
> An ODT cross-reference to the footnote? That makes sense, but should
> that be achieved by footnoting inside a footnote, or is the appropriate
> thing to do to use a dedicated target and link?
>
> [fn:1] footdef1, see also [[thatotherfootnote]].
>
> [fn:2] <>fo
Hello,
Vaidheeswaran C writes:
> That said, it is difficult for me to conceive of a footnote that is
> referenced solely by other footnotes. i.e., it is reasonable to assume
> that a given footnote is either not referenced at all or is referenced
> atleast once in the main text itself.
There's
Hello,
Rainer M Krug writes:
> Please find attached the below described patch including the fix for the
> error reported - function raises error when property value is numeric.
Looks good. Thank you.
Could you provide an appropriate commit message? Bonus points if you
also add a test.
Regards
Nicolas Goaziou writes:
> Hello,
>
> Rainer M Krug writes:
>
>> Please find attached the below described patch including the fix for the
>> error reported - function raises error when property value is numeric.
>
> Looks good. Thank you.
Thanks.
>From 6461f4de49fbcd002913a58ac5b47453e965ac0d M
Hi,
Check:
(let ((org-export-dispatch-use-expert-ui nil))
(mapc 'require '(ox-man ox-md))
(org-export-dispatch))
I guess we could just move man to 'M'?
–Rasmus
--
Governments should be afraid of their people
Hello,
Rasmus writes:
> Cdlatex environment inserted via org-cdlatex-environment-indent are pretty
> bad at getting the right indention. Consider:
>
> - concept :: a long description of concept |
>
> Where | is cursor. When I call org-cdlatex-environment-indent, I expect
>
> - concept
Hello,
Rasmus writes:
> Check:
>
> (let ((org-export-dispatch-use-expert-ui nil))
> (mapc 'require '(ox-man ox-md))
> (org-export-dispatch))
>
> I guess we could just move man to 'M'?
Indeed. Thanks.
Regards,
--
Nicolas Goaziou
Hello,
Yuri Niyazov writes:
If a block agenda exists, with say, agenda on top and todo on the bottom,
then by default it opens to "today". It is possible then to press j and
select a
different date to go to. After that, if we hit "r" to redisplay, we get
different
Hi,
Sometime when requiring custom formatting of the header for a document, it
would be nice to be able to use #+TITLE without triggering the insertion
of the tile (e.g. \maketitle in latex and title in ox-html). For
instance, one might have special org-html-preamble code. This patch adds
an "#+
How about a raw compact guide. The complete guide won't really load into
Emacs very well on my machine.
On Tue, Feb 10, 2015 at 12:18 PM, Rasmus wrote:
> Lawrence Bottorff writes:
>
> > What would the github link be?
>
> https://github.com/tsdye/orgmanual
>
> Tom frequents the list regularly
Hi Stefan,
Stefan Nobis writes:
> Richard Lawrence writes:
>
>> Rasmus writes:
>
>>> Citation types for extracting parts:
>>> citeauthor, citetitle, citeyear, citedate, citeurl,
>
>> As I've said in other posts, I think maybe we should not think of
>> these as `citation' commands and thus
Richard Lawrence writes:
> Conceptually, something like `@key:year' isn't a citation, but merely
> indirection, because it doesn't actually provide the reader of the
> rendered document enough information to look up the reference. I think
> we can cut down on the number of `citation' types that
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
> Richard Lawrence writes:
>
>> Conceptually, something like `@key:year' isn't a citation, but merely
>> indirection, because it doesn't actually provide the reader of the
>> rendered document enough information to look up the reference. I
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Richard Lawrence writes:
>>
>>> Conceptually, something like `@key:year' isn't a citation, but merely
>>> indirection, because it doesn't actually provide the reader of the
>>> rendered document enough inf
On Wednesday 11 February 2015 02:59 AM, Nicolas Goaziou wrote:
Hello,
Vaidheeswaran C writes:
That said, it is difficult for me to conceive of a footnote that is
referenced solely by other footnotes. i.e., it is reasonable to assume
that a given footnote is either not referenced at all or is
On Sat Feb 07 2015 at 10:38, Marcin Borkowski wrote:
> On 2015-02-03, at 06:45, Basile (The Flammable Project)
> wrote:
>
>> Hello,
>>
>> You should have a look at EMMS. It's suite easy to setup on linux. But if
>> you are using a MS Windows OS, it does requiert more settings. But
>> everything
On Wednesday 11 February 2015 02:58 AM, Nicolas Goaziou wrote:
Hello,
Christian Moe writes:
An ODT cross-reference to the footnote? That makes sense, but should
that be achieved by footnoting inside a footnote, or is the appropriate
thing to do to use a dedicated target and link?
[fn:1] f
On Wednesday 11 February 2015 11:32 AM, Vaidheeswaran wrote:
This should be fixed. Thank you.
Not yet. See attached files.
Operator error. Sorry.
64 matches
Mail list logo
