Thanks,
I will try to see if there is something in my config causing the issue.
All best,
Leonard
On 17 September 2015 at 08:26, Nicolas Goaziou
wrote:
> Hello,
>
> Leonard Randall writes:
>
> > I noticed 2 more issues with the include function on latex export.
>
> I
Hi,
I noticed 2 more issues with the include function on latex export. The
first, is that when I make an id link between 2 included files, the
exporter gives the section associated with the linked header the same label
as the header where the link is located. So for instance if I include two
files
Thanks for the help!
On 13 September 2015 at 21:10, Nicolas Goaziou
wrote:
> Hello,
>
> Leonard Randall writes:
>
> > The new smart quotes algorithm does not seem to capture British style
> > quoting (single outer quotes, double inner quotes) correctly. It
> > tre
Hi,
The new smart quotes algorithm does not seem to capture British style
quoting (single outer quotes, double inner quotes) correctly. It treats all
single quotes that are not enclosed in double quotes as apostrophes. I
assume that it was revised to deal with apostrophes that occur on the
outside
that you should know
about the behaviour, as I do not think that it is intended.
All best,
Leonard
On 6 September 2015 at 21:21, Nicolas Goaziou
wrote:
> Hello,
>
> Leonard Randall writes:
>
> > I have my thesis divided into several chapters each with its own org
> file.
> &
Hi org mode community,
I have my thesis divided into several chapters each with its own org file.
I was trying to use org's Include function to compile a pdf of the complete
draft using a master file. However, I found that if there was more than one
reference to the same footnote in one of my chap
Hi all,
In a few functions that I use for organizing my research, I use links
drawers. This enables me to write functions that automatically insert links
in all entries matching particular criteria, or insert links directly from
the headline or anywhere else in the entry. To do this I wrote a coupl
Hi all,
One of the things I really like about org-mode is the ability to quickly
move material between projects. For instance, I sometimes write material as
a conference paper and want to use some sections in my thesis. I also like
to keep a file with old chapter drafts for later reference (I could
Hi Bastien,
Just to follow up on the error, reverting commit 0ca4092 fixes the bug that
I mentioned in my last email and reverting the fourth hunk of commit
b8c85a1 should fix the bug that you tried to fix with that commit. Carsten
had added an 'unless (bolp)' condition to the function that contr
Hi Bastien,
Thanks for the fix, and sorry to be the bearer of bad news, but there seems
to be a new issue. Now, if you press M-RET in a lower level tree anywhere
but in the headline, it will produce a new first level headline. So, given
buffer contents as in example (a), if i press M-Ret at the end
On 29 April 2014 15:20, Bastien wrote:
>
> I'm having a hard time finding out what you *did* exactly -- can you
> describe the way to reproduce the bug from an empty buffer, step by
> step?
>
Sorry, I should have been more explicit about what I was doing. Step by
step instructions would look som
Hi Bastien,
On 29 April 2014 13:08, Bastien wrote:
>
> I guess so -- show us the code and we will be able to tell :)
>
> Thanks, I will try to get something workable by late this weekend. Also, I
will let you know as soon as FSF authorizes my paperwork.
All best,
Leonard
f a file. But will not work
on the second. This is what I got:
---
* this is a test
*
this is another
---
As I say M-Ret worked fine on the first line, but inserted a new line when
called on the second.
All best,
Leonard
On 29 April 2014 13:35, Bastien wrote:
> Hi Leonard,
>
>
Hi Will,
The example works fine for me. It seems like the most likely cause of your
issue is your export settings. One thing that you might try is to add this
to the top of your file.
#+Options: *:t
If you already have an options section on your file you may want to check
that you do not have *:
Hi Julian et al.,
I am not sure if this helps, but I am in the process of writing a new
package for inserting citations into org buffers using RefTeX. This
solution would make citation insertion very convenient, but it would not be
quite as easy to read as Clément's solution, and it would only work
Dear All,
I am in the process of writing a new package for inserting citations into
org buffers using RefTeX. The current org-reftex command works alright, but
it is not quite as flexible as I would like it to be. I wanted to add an
option to add citations in footnotes. I also wanted to make it so
Hi Bastien,
On 25 April 2014 08:29, Bastien wrote:
> I just fixed this in maint -- please let me know if it works
> back as expected.
>
Yes, now C-RET and the speedkey `i' now function as
described in the documentation. The only place where the
function differs from the documentation is at the
Hi Sharon,
On 24 April 2014 04:47, Sharon Kimble wrote:
> In my agenda I have several items I call my "weeklies" because they repeat
> weekly, this is one of them -
> --8<---cut here---start->8---
> Desert island discs - radio 2 @ 1100
> SCHEDULED: <2014-04-27
Sorry, I should clarify that the C-RET functions as expected in the content
of an entry, it is only problematic when it is called from the headline.
All best,
Leonard
On 23 April 2014 22:42, Leonard Randall wrote:
> Hi Bastien,
> I just wanted to report an issue with this fix. In ma
Hi Bastien,
I just wanted to report an issue with this fix. In many use cases it makes
C-RET less useful, and renders the speedkeys command `i' useless. It makes
C-RET function much like M-RET, and it makes `i' insert headlines before
any content.
So if I call C-RET in the middle of the following
Thanks!
On 20 April 2014 07:31, Bastien wrote:
> Hi Leonard,
>
> (you forgot to copy the list I think.)
>
> I finally committed your solution, convinced by your tests.
>
> Now we reached the limit for the changes, let's wait until the
> FSF confirms you can contribute more code.
>
> Thanks agai
Hi Bastien,
Bastien wrote:
> I fixed this by ignoring the error, since the field is inserted
> anyway.
For some reason ignoring errors doesn't work for me. The new function,
doesn't add a keywords field to non-standard bib entry types, it just puts
the tags before the beginning of the bibtex en
Hi Bastien et. al,
I figured out how to fix the bug i reported awhile ago. The problem was
that when making the keyword field for entries without keywords defined in
the `:PROPERTIES:' drawer, org-bibtex uses `bibtex-make-field' from
`bibtex.el'. This function sends up an error if there are no fie
; where it should read
`org-bibtex-headline'.
I have also figured out that bug I mentioned. More on that in a minute.
Thanks,
Leonard
On 18 April 2014 15:47, Bastien wrote:
> Hi Leonard,
>
> Leonard Randall writes:
>
> > Thanks for the feedback. I have attached the mo
Hi Bastien,
Thanks for the feedback. I have attached the modified patch.
All best,
Leonard
On 18 April 2014 12:14, Bastien wrote:
> Hi Leonard,
>
> thanks for starting this! A few stylistic comments inline.
>
> Leonard Randall writes:
>
> > diff --git a/lisp/
oc strings to reflect the change. I also
edited one doc string that seemed to refer to an old variable that is no
longer in use.
On 17 April 2014 15:25, Bastien wrote:
> Hi Leonard,
>
> Leonard Randall writes:
>
> > Unfortunately, my knowledge of lisp is particularly rudimentar
eonard
On Fri, Apr 4, 2014 at 11:43 AM, Leonard Randall <
leonard.a.rand...@gmail.com> wrote:
> Hi,
> Right now when you run org-bibtex with org-bibtex-tags-are-keywords set to
> true, only the tags assigned directly to the headline are converted. So for
> instance if run org bibtex on
Hi,
Right now when you run org-bibtex with org-bibtex-tags-are-keywords set to
true, only the tags assigned directly to the headline are converted. So for
instance if run org bibtex on a file set up like this.
* Authority :auth:
** Kant's Views on authority :Kant:
:properties:
(bibliography info h
Hello,
When I attempt to run M-x org-bibtex on a .org file with non-standard
bibtex types that have a tag, they fail to export if
org-bibtex-tags-are-keywords is set to t. This persists even if I add the
bibtex type to org-bibtex-types. I checked, and this problem persists with
a minimal init fil
Hello,
When I attempt to run M-x org-bibtex on a .org file with non-standard
bibtex types that have a tag, they fail to export if
org-bibtex-tags-are-keywords is set to t. This persists even if I add the
bibtex type to org-bibtex-types. I checked, and this problem persists with
a minimal init fil
30 matches
Mail list logo
