On Thu, Sep 2, 2010 at 6:15 PM, Carsten Dominik
wrote:
>
> On Sep 1, 2010, at 12:19 AM, Alan L Tyree wrote:
>
> On Tue, 31 Aug 2010 14:09:58 +0200
>> Carsten Dominik wrote:
>>
>> Hi Aidan,
>>>
>>> unfortunately this is difficult to fix in a good way.
>>> I do want to go back to footnotes, becau
On Sun, Feb 20, 2011 at 6:53 PM, Achim Gratz wrote:
> Christian Moe writes:
> > I agree exporting 'chapters' in a single Org document to separate html
> > files would be a nice option to have.
> >
> > Pending someone writing an export function for this, you could
> [...]
>
> That sort of already
On Mon, Feb 28, 2011 at 7:48 PM, Julien Danjou wrote:
> On Mon, Feb 28 2011, Alan L Tyree wrote:
>
> > The development list wouldn't be very interesting without the intense
> > interaction that it now has with users. The org list seems unique in
> > this, at least for the lists that I have someti
Lyx is brilliant - I used it to typeset a cookbook that my wife wrote and
then I wrote a small text "Self-publishing with LyX". Anyone can learn to
use it in a short time.
It was my first thought, but unfortunately there doesn't seem to be an easy
way to import LaTeX where the LaTeX file has multi
There must be something more than this. I sometimes work on a similar size
file on an HP Chromebook using emacs in a Crouton installation and have no
problems at all with speed. It is a nox emacs installation, if that matters.
Alan
On 11 July 2016 at 08:34, John Kitchin wrote:
> I find it somet
Pandoc can pull a web page, convert to Markdown and then to Org. That
doesn't do all you want, but maybe a start.
Cheers,
Alan
On 16 March 2014 05:03, Xebar Saram wrote:
> Thanks so much for the tips Erik
>
> i will explore the ingredients in table idea as suggested. do you know
> perhaps of a
Unless you have the structure of your book set in stone, numbers just get
in your way. The great power of org is being able to write 'modularly' and
rearrange at will.
When you export, your chapter/section numbers will be right as well as all
cross references.
I think you'll be happier to ignore
I was trying to build a keyboard macro to remove targets of the form
<>
When in org-mode, emacs hangs after C-s <. If I turn off org mode and use a
simple text mode, the keyboard macro works ok.
Is this a bug or am I doing something pretty dumb?
Thanks,
Alan
emacs version: 24.3.1 on Ubuntu 14.
Hi Eric,
My "solution" was a keyboard macro at the LaTeX stage, replacing
\ref{sec-3-2-1} with 3.2.1 in the text.
Not very elegant, but it works for the time being when I don't have the
time to consider anything better.
A filter would obviously be better, but my elisp skills mean that it would
t
Hi Steven,
You want to learn more about LaTeX, but it's not too much.
I wrote a little book called Self-publishing with LyX that will help you
set up the title page as well as some of your other problems. This is not a
sales pitch -- it's free :-).
Self-publishing with LyX
ISBN: 978-0-9803-3242-
Thanks for the kind words, Martin. I hope you stay inspired since making a
few homemade paperbacks sounds like something I'd like to try.
Cheers,
Alan
On 31 May 2014 17:25, Martin Schöön wrote:
> On 28 May 2014 06:31, Alan Tyree wrote:
>
>> Hi Steven,
>> You want to
Is this the way it should be? The first DEADLINE: shows up both as a
warning and on the due date in the agenda, but the second one does not. It
only works for me if the DEADLINE: is the first line after the heading.
Version 9, emacs 24
*** test 1
DEADLINE: <2016-11-19 Sat>
*** test 2
DEADLINE: <
On 10 November 2016 at 10:36, Nicolas Goaziou
wrote:
> Hello,
>
> Alan L Tyree writes:
>
> > On 10/11/16 05:51, Philip Hudson wrote:
>
> > Also, if this really is the case, then the manual needs to be
> > modified. Under 8.1, it says
> >
> > " A timestamp can appear anywhere in the headline or b
On 10 November 2016 at 10:47, Samuel Wales wrote:
> iirc we've discussed whether planning lines (i.e. scheduled, deadline,
> closed at this time) should be flexible. we concluded to make them
> strict.
>
> check archives for the discussion. :) everything goes through this
> mailing list.
>
> OK
On 11 November 2016 at 02:08, Nicolas Goaziou
wrote:
> Hello,
>
> Alan Tyree writes:
>
> > Suggested wording:
> >
> > In 8.1:
> >
> >
> > timestamp can appear anywhere in the headline or body of an Org tree
> > entr UNLESS is is p
On 11 November 2016 at 11:12, Nicolas Goaziou
wrote:
> Alan Tyree writes:
>
> > Will you please double check this? On my system, the entry does *not*
> show
> > up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show
> > up. So, for the important pu
I don't know if this helps, but I am running Manjaro, using the repository
packages and have no problem with export. The installed texlive packages
are:
texlive-bin
texlive-core
texlive-humanities
texlive-latexextra
I have no problems with either org export or any pandoc conversions.
Cheers,
Ala
I'm a non-technical user, and I've never used ysnippets, but I'm willing to
give it a go with some proper instruction.
I do see the argument of both sides.
Here is a question: I see specialised snippet packages in the ELPA
respositories. Is it possible to provide snippets that reproduce the
exist
G'day,
I have a citation problem. The bibtex entry is:
@TechReport{name32:_some,
author = {{Some Company Name}},
title = {Some silly internal document},
institution = {Some Company Name Ltd},
year = 1832}
The exporter is: #+cite_export: csl ~/Templates/csl/AGLC-intext.csl
Org exports to
gt;
> On Wed, May 4, 2022, 8:19 PM Alan Tyree wrote:
>
>> G'day,
>> I have a citation problem. The bibtex entry is:
>> @TechReport{name32:_some,
>> author = {{Some Company Name}},
>> title = {Some silly internal document},
>> institution = {Som
ate citeproc-el. I'm not sure when he tagged v0.9, but this is
> the commit that should have fixed it.
>
>
> https://github.com/andras-simonyi/citeproc-el/commit/a702e73dcbd34cbda3a7465cf0cace7529f41dcd
>
> If you still have problems, you might report it to that project?
>
I need some help with a debugging problem:
I'm using
#+cite_export: csl ~/Templates/csl/AGLC-intext.csl
where AGLC-intext.csl is a custom csl file.
Exporting to html gives this error in *Messages*:
citeproc-s-slice-by-matches: Wrong type argument: stringp, nil
The error does not occur with di
uld still be helpful to be able to find it.
Cheers,
Alan
On Mon, 6 Jun 2022 at 09:15, Bruce D'Arcus wrote:
> On Sun, Jun 5, 2022 at 6:48 PM Alan Tyree wrote:
>
> > I need some help with a debugging problem:
> >
> > I'm using
> >
> > #+cite_export:
}} works fine;
author = {{Wolfsberg}} chokes.
Thanks to you and to Bruce for the help.
Cheers,
Alan
On Mon, 6 Jun 2022 at 11:03, Ihor Radchenko wrote:
> Alan Tyree writes:
>
> > I guess the bad news is that the csl file validates. I also should have
> > mentioned that everythi
Hi Andras,
I will do that. Thanks to all of you for your help and for the great
system. I cannot believe that I once wrote using word processors!!
Cheers,
Alan
On Mon, 6 Jun 2022 at 15:34, András Simonyi
wrote:
> Dear All,
>
> On Mon, 6 Jun 2022 at 03:45, Alan Tyree wrote:
>
> &
3 days, 2 hours, 25 minutes, 36 seconds
2.35% of cache searches hashed, 78.11% non-hashable.
Org mode version 9.6.1 ( @ /home/alant/.emacs.d/elpa/org-9.6.1/)
On Fri, 10 Feb 2023 at 22:18, Fraga, Eric wrote:
> 10.48% of cache searches hashed, 5.66% non-hashable.
> 2 days, 17 hours, 12 minutes
26 matches
Mail list logo
