On Sat, Feb 20, 2021 at 10:31 PM Adam Sneller wrote:
> I currently use org-ref and helm-bibtex to manage my database of academic
> sources, with one notes file per source. A lot of my sources are books. So
> note typically grow over time, as I add multiple headers (each pertaining to
> a chapt
> When exporting a subtree, the top-level outline becomes the title of the
> document, i.e., the document becomes morally equivalent to:
>
> #+title: test
> <2021-03-18 Thu 15:00-16:00>
> body of text
>
> There is indeed no event to export in this case. Only level 2 outline
> will bec
In org-ref you also handle this by annotations of the cite links, e.g.
[[cite:book-key][p23]] and then bibtex or biblatex does the formatting.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburg
Hi,
Tim Cross writes:
> If a line starts with a number, period and space, but that line is
> within a paragraph (i.e. no blank line above), then I don't think it
> should be interpreted as an enumerated list item. If this is what the OP
> is referring to, I would argue it is a bug. If it is a 'p
Thanks Tim and Greg. I had mostly come to the same conclusions that it is
probably best to outsource this. I worked out some examples from
the orgtbljoin and orgaggregate packages with Pandas below, in case anyone
is interested in seeing how it works. A key point is using the ":colnames
no" header
On 2021-02-21 01:23, Kyle Meyer writes:
> Okay, thanks for checking. Added a basic test and applied (3a522ad53).
Great, thanks a lot!
Best,
Alan
signature.asc
Description: PGP signature
For fun, here is the sqlite equivalent of the Pandas example using the same
tables as before
** aggregation example
Examples from https://github.com/tbanel/orgaggregate
#+NAME: original
| Day | Color | Level | Quantity |
|---+---+---+--|
| Monday| Red |3
Hi Bruce/John,
Thanks for getting back to me. So I guess your notes file would look something
like this?
#+TITLE: Bradley, J. (1973): Essential Mathematics For Economists
* Dynamic models: the consumption function
[[cite:bradley1973es][p164]]
* Changes in Capital Stock
[[cite:bradley1973es][p
It seems like some ideas are getting mixed up in your description. A cite
link in org-ref is related to a bibtex entry in a bibtex file, not to an
org heading in an org-file. In other words in your example, I would expecta
bibtex entry with the key bradley1973es to exist in one of the default
bibli
Thanks John!
I think you have just given me my next homework assignment for "Adam's list of
things to noodle around with in eLisp" :)
Adam
> On 21 Feb 2021, at 17:40, John Kitchin wrote:
>
> It seems like some ideas are getting mixed up in your description. A cite
> link in org-ref is related
Kyle Meyer writes:
> It seems that your approach would do a good job of helping you catch
> cases that you don't want to be treated as lists. I'm not aware of any
> related functionality in Org, so I don't think you're missing something
> there.
>
> Once you know that there is a particular spot
Juan Manuel,
YMMV depending on your needs and habits, but another workaround for this
problem would be to use visual-line-mode instead of filling paragraphs.
--Diego
On Sun, Feb 21, 2021 at 8:34 PM Juan Manuel Macías
wrote:
> Kyle Meyer writes:
>
> > It seems that your approach would do a
perhaps if there is no blank line above or below, then it could be not a list.
On 2/21/21, Diego Zamboni wrote:
> Juan Manuel,
>
> YMMV depending on your needs and habits, but another workaround for this
> problem would be to use visual-line-mode instead of filling paragraphs.
>
> --Diego
>
>
>
Samuel Wales writes:
> perhaps if there is no blank line above or below, then it could be not a list.
I think this solution would be fine, although plain paragraphs starting
with digit/letter + period + space would be false positives. Anyway,
some kind of highlighting in the items, a defined fac
Diego Zamboni writes:
> Juan Manuel,
>
> YMMV depending on your needs and habits, but another workaround for this
> problem would be to use visual-line-mode instead of filling paragraphs.
Note that filling paragraphs in Org should already guard against
inadvertently creating a list item. (Some r
Juan Manuel Macías writes:
> Kyle Meyer writes:
>
>> It seems that your approach would do a good job of helping you catch
>> cases that you don't want to be treated as lists. I'm not aware of any
>> related functionality in Org, so I don't think you're missing something
>> there.
>>
>> Once you
Samuel Wales writes:
> perhaps if there is no blank line above or below, then it could be not a list.
>
Initially, that was my thought as well. Unfortunately, it isn't quite
that straight forward. Consider the list
1. Item 1
2. Item 2
3. Item 3
The second item has no blank lin
Tim Cross writes:
> The issue is, if we decide this is a bug, can we fix it? Is it a bug or
> is it just an accepted limitation of the org document format and what we
> have to do is ensure either no line starts with a '1. ' or we use
> something like a unicode character so that it doesn't look l
Tim,
> If a line starts with a number, period and space, but that line is
> within a paragraph (i.e. no blank line above), then I don't think it
> should be interpreted as an enumerated list item. If this is what the OP
> is referring to, I would argue it is a bug. If it is a 'paragraph'
> startin
Greg Minshall writes:
> Tim,
>
>> If a line starts with a number, period and space, but that line is
>> within a paragraph (i.e. no blank line above), then I don't think it
>> should be interpreted as an enumerated list item. If this is what the OP
>> is referring to, I would argue it is a bug.
Tim,
> There is no plans to change anything as far as I know. What I wrote was
> mainly to show why we have the situation and that any proposed solution
> has its own drawbacks.
thanks. (i assumed that, but ...)
> Bottom line, we cannot easily prevent the 'false' list item issue
> without intro
John,
Checkout what R sqldf package makes easy:
** aggregation example
Examples from https://github.com/tbanel/orgaggregate
#+NAME: original
| Day | Color | Level | Quantity |
|---+---+---+--|
| Monday| Red |30 | 11 |
| Monday| Blue |25 |
22 matches
Mail list logo
