Richard Lawrence writes:
> Rasmus writes:
>> Parts I hate:
>> The flag is either `@' or `&'. `@' [...] The optional hyphen (`-')
>> Too many weird symbols that I won't be able to remember, much less explain
>> to somebody else.
> I don't love these either, but I am not sure what a bett
Hello,
Matt Price writes:
> However, I agree that the distinction between parenthetical and footnotes
> citations is unhelpful for me. Whenever I switch between Chicago and APA,
> for instance, zotero converts my footnotes to parenthetical expressions.
> To me this seems an essential feature.
Hi Marcin,
Marcin Borkowski wrote:
> I don't want to be nitpicking, but I'm just curious. I'm looking at the
> function `org-split-string'. It uses (two times) the following
> construction:
>
> (setq list (cons (something) list))
>
> Is there any particular reason for not using `push' there?
II
Hello,
Nikolai Weibull writes:
> Sorry for the late reply. Here’s a patch that should work:
Thank you.
Could you provide an appropriate commit message and send it using git
format-patch? If you haven't signed FSF papers yet, you also need to add
TINYCHANGE at the end of the commit message.
Nicolas Goaziou writes:
> Time for another crazy idea. Last one on my side for today
> [cite ...] [(cite) ...] [Cite ...] [(Cite) ...]
> It should solve the :capitalize issue.
+1
I really like it - even when looking at the org file with something
weird like vim, it's very clear and intuitiv
Matt Price writes:
> I am generally much more positive than Thomas, being, for the most part,
> ecstatic at the thought of a built-in citation syntax which will make
> citations in org workable for bumbling nonprogrammers like myself.
>
> However, I agree that the distinction between parenthet
Hi there,
I think I must be missing something.
I have a collection of articles in one org file (under separate
headings). I can export these as a subtree using Org's normal export
function as html etc., but I want to export the selected subtree as an
individual org file using the properties unde
Nicolas Goaziou writes:
>> <2015-02-13 ven.> (10h-13h)
>>
>> Hiting C-c . RET with point on the timestamp gives
>> <2015-02-13 ven. -13h> (10h-13h)
>>
>> which is not expected.
>
> It should now be fixed.
>
Thanks, works great so far (unlike my own patch, which would fail in
some situations).
--
On Saturday, 14 Feb 2015 at 18:29, Richard Lawrence wrote:
> Hi everyone,
>
> Since discussion seems to have petered out on the previous thread (see:
> http://thread.gmane.org/gmane.emacs.orgmode/94524), I took some time to
> go back over the discussion and write up a concrete proposal for
> citati
I have set up only one persistent tag set with a key character like this:
(org-tag-persistent-alist (quote (("@i_shopping" . 105
There are no file based #+TAGS in any of org files.
I also like to have access to all tags in all files, so I set this up:
(org-complete-tags-always-offer-all-agend
Change :EXPORT_FILENAME: an-interesting-article to :EXPORT_FILE_NAME:
an-interesting-article
Then,
C-c C-e C-s O o
should export to that file. I notice in the org export that the
properties are not getting exported, and even the headline is not
exported as the title though.
Here is a function t
+1 from me too, observing from the sidelines but also wanting to be able to
handle citations.
Bill
On 16 February 2015, Eric S Fraga wrote:
On Saturday, 14 Feb 2015 at 18:29, Richard Lawrence wrote:
Hi everyone,
Since discussion seems to have petered out on the previous thread (see:
http://
Presumably this is related to my having upgraded to:
Org-mode version 8.2.10 (8.2.10-33-g880a2b-elpa)
GNU Emacs 25.0.50.6 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.9) of
2015-02-10 on localhost.localdomain
I use org-contacts[1] to autofill addresses in GNUs. Normally can use
"+CATEGORY" to ad
Eric S Fraga writes:
> On Saturday, 14 Feb 2015 at 18:29, Richard Lawrence wrote:
>> Hi everyone,
>>
>> Since discussion seems to have petered out on the previous thread (see:
>> http://thread.gmane.org/gmane.emacs.orgmode/94524), I took some time to
>> go back over the discussion and write up a
Thanks very much for this John. As you say, the normal export "C-c C-e
C-s O o" does not work as expected. Your function exported the
properties properly, but seemed to work on the visible text only and
wouldn't export the content of headings (unless I unfold them all prior
to import). If the art
Hello all,
Please ignore my previous email. I have rebuilt org and restarted emacs
and everything is back to normal. I don't know why a particular key
binding disappeared but maybe it was a cosmic ray incident :)
[[http://xkcd.com/378/]]
Sorry for the noise.
--
: Eric S Fraga (0xFFFCF67D), E
I think if you change (org-org-export-as-org nil t t) to
(org-org-export-as-org nil t) you would get the section content. I
didn't test it though.
si...@psilas.com writes:
> Thanks very much for this John. As you say, the normal export "C-c C-e
> C-s O o" does not work as expected. Your function
Dear Org-users,
I got this table:
| Menge (x) | P(x) | E(x) | K(x) | Gewinn |
|---+--+++-|
| 0 | 20 | 0.00 | 140.00 | -140.00 |
|10 | 18 | 180.00 | 180.00 | 0.00|
|20 | 16 | 320.00 | 220.00 | 100.00 |
|30 | 14
That's perfect John, works a treat!
Thank you very much.
Simon.
---
On Mon, 16 Feb 2015, at 02:59 PM, John Kitchin wrote:
> I think if you change (org-org-export-as-org nil t t) to
> (org-org-export-as-org nil t) you would get the section content. I
> didn't test it though.
>
> si...@psilas
John Kitchin writes:
> I still remain somewhat on the positive side of 0. While the focus of
> these conversations has been on syntax (a necessary step to move
> forward), there has been little focus on function.
One step at a time. It's already difficult to agree on a syntax.
> Citations in or
Hi Eric,
Eric S Fraga writes:
> +1 emphatically.
Thanks!
> With respect to the bibliography database, for completeness, I would
> like to see linking with org-bibtex data instead of bibtex etc.
Me too, as I keep all my reference data in org-bibtex. I suggest we
discuss the bibliography and o
0.
John Kitchin writes:
Citations in org are /far/ more than just references in the text
for me. They are functional links, gateways to a lot of
information connected to the citation. My org-files are much
more useful than the PDF manuscripts that get exported.
I completely agree.
I also
Hi John,
I don't have time for a long reply but I wanted to express a couple
points of agreement:
John Kitchin writes:
> I think the usual suspects reftex, helm-bibtex, and probably ebib
> could be taught to output most of this syntax for whatever type, and
> they could give human readable hint
Hi Nicolas,
Nicolas Goaziou writes:
> Time for another crazy idea. Last one on my side for today
>
> [cite ...] [(cite) ...] [Cite ...] [(Cite) ...]
>
> It should solve the :capitalize issue.
I am OK with this if it is important, though I am a little hesitant.
In the last thread, you express
Hello all,
(I hope this is not just noise...)
I use org as my main writing tool, typically for publications that I
submit using LaTeX. So far, so excellent!
However, I do have to export to ODT (as a means to DOC) and I find the
export to be very fragile. I keep running into some strange error
Nicolas Goaziou writes:
> John Kitchin writes:
>
>> I still remain somewhat on the positive side of 0. While the focus of
>> these conversations has been on syntax (a necessary step to move
>> forward), there has been little focus on function.
>
> One step at a time. It's already difficult to ag
Richard Lawrence writes:
> I am OK with this if it is important, though I am a little hesitant.
I don't know if it is important. Just thinking out loud.
> In the last thread, you expressed concern that we not have too much
> variation after the opening `[' for performance reasons, which is why
Aloha Stefan,
Stefan Nobis writes:
> Richard Lawrence writes:
>
>> Rasmus writes:
>
>>> Parts I hate:
>
>>> The flag is either `@' or `&'. `@' [...] The optional hyphen (`-')
>
>>> Too many weird symbols that I won't be able to remember, much less explain
>>> to somebody else.
>
>> I don
jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
> From what I read in this and the previous thread, the new proposal
> tries more or less to reimplement BibTeX in org.
No, that's wrong, not the database should be replaced. The goal is to
make citations a first class citizen in the
>
>> There is no question in my mind that some people will want to extend
>> this, as there are just too few of the latex citation commands
>> supported out of the box, especially for biblatex users (who used that
>> because of limitations in bibtex ;).
>
> Do you think there are important command
Stefan Nobis writes:
> jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
>
>
> Hmmm... nowadays one uses biblatex[fn:1] (with its companion biber)
> which makes hacking bibliography styles quite easy (in LaTeX; compared
> to customizing bst files). I do not think that the current di
Nicolas Goaziou writes:
> [cite:subtype: ...]
>
> where "subtype" can be associated to any number of attributes, at user's
> discretion.
I like CITE:subtype for customization, where CITE is a member some set,
e.g. {cite citep/(cite) fncite citeauthor} or whatever. I like this cause
it's ∞ cust
John Kitchin writes:
Stefan Nobis writes:
Hmmm... nowadays one uses biblatex[fn:1] (with its companion
biber) which makes hacking bibliography styles quite easy (in
LaTeX; compared to customizing bst files). I do not think that
the current discussion will lead to writing bib-styles in Lisp
John Kitchin writes:
> They are probably minor, but for example I am not sure how easy it would
> be to sort a multicite with all of the syntax options. I guess it can be
> done, I just do not see it clearly. It may not be necessary to do this
> either.
Out of curiosity:
Why would this be hard?
Here is one way to do it in a code block.
#+tblname: tab-data
| Menge (x) | P(x) | E(x) | K(x) | Gewinn |
|---+--+++-|
| 0 | 20 | 0.00 | 140.00 | -140.00 |
|10 | 18 | 180.00 | 180.00 | 0.00|
|20 | 16 | 320.00 | 220.00 | 1
Nicolas Goaziou writes:
> Rasmus writes:
>
>> But footnotes in titles are set with symbols, e.g. * † ‡ and so forth.
>> IOW they are independent of the regular footnote counter, and don't
>> consume a number.
>
> But then it requires to implement a special handler in every export
> back-end and
That is probably something like it. I meant sorted by year (others may
prefer author), which also means looking up in the database, decorating,
and then sorting, but that doesn't fundamentally change your idea. Then,
from the sorted list, you have to regenerate the org-syntax and replace
the origin
Rasmus writes:
> Biblatex is the gold standard. Maybe not in input-aesthetics..., but in
> terms of amenability, usability and output it surely is. (No, I have
> nothing to back this up).
Compare the bibtex style, chicago.bst, with biblatex-chicago and note
how much more closely the biblatex v
Stefan Nobis writes:
jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
From what I read in this and the previous thread, the new
proposal tries more or less to reimplement BibTeX in org.
No, that's wrong, not the database should be replaced. The goal
is to make citations a fi
t...@tsdye.com (Thomas S. Dye) writes:
>> Biblatex is the gold standard. Maybe not in input-aesthetics..., but in
>> terms of amenability, usability and output it surely is. (No, I have
>> nothing to back this up).
>
> Compare the bibtex style, chicago.bst, with biblatex-chicago and note
> how m
Hi Thorsten
On Mon, Feb 16, 2015 at 4:01 PM, Thorsten Grothe wrote:
> I got this table:
>
> | Menge (x) | P(x) | E(x) | K(x) | Gewinn |
> |---+--+++-|
> | 0 | 20 | 0.00 | 140.00 | -140.00 |
> |10 | 18 | 180.00 | 180.00 | 0.00|
> |
Hello,
Eric S Fraga writes:
> At this point, I get very long data structures dumped to
> *Messages*... difficult to figure out what is wrong. It's often my
> mistake but tracking it down is difficult.
You're using an internal link to target a paragraph (possibly a image or
some such). This is
Hello,
As explained in its commit message, the following patch is an attempt at
simplifying `org-show-context' configuration by offering a set of
5 predefined views to choose from instead of setting 4 different
variables (`org-show-following-heading', `org-show-siblings',
`org-show-entry-below' an
Hi,
A caption seems to prevent Org from finding a table when using inline
calls. Consider this example:
#+NAME: tbl0
#+CAPTION: caption
| a | b |
|---+---|
| 1 | 2 |
src_emacs-lisp[:var val=tbl0[2,1]]{val} =nil=
#+CAPTION: caption
#+NAME: tbl1
| a | b |
|---+---|
| 1 | 2 |
src_emacs-lisp[:va
Thank you John and Michael for your suggestions, I will see if my
knowledge is wide enough to understand this, unfortunately I'm a emacs
newbie :-)
Anyway I will answer after testing your suggestions!
Regards
Thorsten
Hello,
Rasmus writes:
> A caption seems to prevent Org from finding a table when using inline
> calls. Consider this example:
>
> #+NAME: tbl0
> #+CAPTION: caption
> | a | b |
> |---+---|
> | 1 | 2 |
>
> src_emacs-lisp[:var val=tbl0[2,1]]{val} =nil=
>
> #+CAPTION: caption
> #+NAME: tbl1
> | a
Hello,
Sebastien Vauban
writes:
> I guess it's directly linked to a problem I reported last
> September. This is indeed annoying...
>
> See issue #29 on http://orgmode.org/worg/org-issues.html (and see the
> pointed thread).
This isssue seems fixed. Can you confirm it?
Regards,
--
Nicolas
Nicolas Goaziou wrote:
> As explained in its commit message, the following patch is an attempt at
> simplifying `org-show-context' configuration by offering a set of
> 5 predefined views to choose from instead of setting 4 different
> variables (`org-show-following-heading', `org-show-siblings',
>
Kyle Meyer writes:
Thanks for the feedback.
> Minor: It took me some extra effort to parse this sentence because I'm
> not used to seeing 'respectively' used in this way. I think something
> like below is more common.
>
> As special cases, a nil or t value means show all contexts in
> `mini
Hi,
> Another idea: [...]
Good trick. I used it in attached, which I think works well.
—Rasmus
--
With monopolies the cake is a lie!
>From 4ab1df88e5bf87d01594e280af7887cc6cd0d3ca Mon Sep 17 00:00:00 2001
From: rasmus
Date: Tue, 10 Feb 2015 12:02:59 +0100
Subject: [PATCH] org.el: Change inde
jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
> I see, so in the examples provided Doe99 is only the key, org would
> not have to know that the author name is Doe and its year is 1999,
> or any other information about the citation.
Yes and no. In the first place org should only
51 matches
Mail list logo
