Achim Gratz writes:
> Alan Schmitt writes:
>> I'll commit as soon as I can find the magic git incantations to get rid
>> of the "merge" commits that happened as I was pulling changes from the
>> repository.
>
> Just cherry-pick your changes on top of the new master or use the
> rewrite facility in
Hi Alan,
Achim Gratz writes:
> Alan Schmitt writes:
>> I'll commit as soon as I can find the magic git incantations to get rid
>> of the "merge" commits that happened as I was pulling changes from the
>> repository.
>
> Just cherry-pick your changes on top of the new master or use the
> rewrite
Alan Schmitt writes:
> I'll commit as soon as I can find the magic git incantations to get rid
> of the "merge" commits that happened as I was pulling changes from the
> repository.
Just cherry-pick your changes on top of the new master or use the
rewrite facility in magit. If you want to avoid t
Nicolas Goaziou writes:
>> By "validating", do you mean that I have received them back signed from
>> the FSF? (I signed and sent them a few weeks ago, still waiting to get
>> them back ...)
>
> Yes. We have to wait for confirmation from the FSF. It shouldn't be too
> long now.
I have received th
Achim Gratz writes:
> Alan Schmitt writes:
>> In other words, I see three places of interest:
>> - where the org file is
>> - where export and compilation occurs
>> - where the final result is put
>>
>> Publishing lets us deal with the last one, but I don't think there is a
>> way to distinguish
Alan Schmitt writes:
> In other words, I see three places of interest:
> - where the org file is
> - where export and compilation occurs
> - where the final result is put
>
> Publishing lets us deal with the last one, but I don't think there is a
> way to distinguish between the first two.
Having
Alan Schmitt writes:
> In other words, I see three places of interest:
> - where the org file is
> - where export and compilation occurs
> - where the final result is put
>
> Publishing lets us deal with the last one, but I don't think there is a
> way to distinguish between the first two.
No, t
Alan Schmitt writes:
> I understand it. What I actually would like is to be able to specify a
> different "working directory". Right now it defaults to the directory
> where the org file is, but it's often not satisfactory (especially when
> compilation creates additional files). Would this be di
Nicolas Goaziou writes:
> Alan Schmitt writes:
>
>> I understand it. What I actually would like is to be able to specify a
>> different "working directory". Right now it defaults to the directory
>> where the org file is, but it's often not satisfactory (especially when
>> compilation creates ad
Nicolas Goaziou writes:
> There is no #+EXPORT_FILE_NAME: keyword. But there is
> an :EXPORT_FILE_NAME: node-property for subtree export. There could be
> a #+FILE_NAME: keyword (much like :EXPORT_AUTHOR: and #+AUTHOR). Though,
> it is too dangerous to my liking.
>
> For example, publishing expec
Hello,
Alan Schmitt writes:
> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
> when I export it (either to beamer or to latex), it's using the name of
> the file instead of the given file name.
>
> Am I doing something wrong here?
There is no #+EXPORT_FILE_NAME: keyword.
Suvayu Ali writes:
> The FSF now accepts scans of the signed form I believe. So the process
> can be completed without using snail-mail.
The snail mail part wasn't the limiting factor, at least in my case.
:-)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld
Suvayu Ali writes:
> On Sun, Dec 09, 2012 at 12:04:18PM +0100, Achim Gratz wrote:
>> Alan Schmitt writes:
>> > I have actually signed and sent the papers to the FSF, I'm waiting to
>> > get them back. Nevertheless it may be good to clarify whether the
>> > TINYCHANGE restriction applies to files
On Sun, Dec 09, 2012 at 12:04:18PM +0100, Achim Gratz wrote:
> Alan Schmitt writes:
> > I have actually signed and sent the papers to the FSF, I'm waiting to
> > get them back. Nevertheless it may be good to clarify whether the
> > TINYCHANGE restriction applies to files in contrib.
>
> Then I wou
Alan Schmitt writes:
> OK, there's something I'm missing here. First, the patch is a copy of
> the same functions in org-e-latex with about 100 characters modified (by
> repeatedly renaming "latex" into "beamer" in several places). I thought
> it would qualify for a "TINYCHANGE", but I guess this j
Achim Gratz writes:
> Alan Schmitt writes:
>> TINYCHANGE
>
> As much as you would wish it wasn't so, your patch exceeds the tiny
> change limit (not even counting your previous contributions) and you'll
> need signed copyright papers for this to go into Org and Emacs.
OK, there's something I'm m
Alan Schmitt writes:
> TINYCHANGE
As much as you would wish it wasn't so, your patch exceeds the tiny
change limit (not even counting your previous contributions) and you'll
need signed copyright papers for this to go into Org and Emacs.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron mic
On Sat, Dec 08, 2012 at 12:13:30PM +0100, Alan Schmitt wrote:
> Alan Schmitt writes:
>
> > I'll try to see if adding beamer support is difficult.
>
> It was trivial to add. Please find a patch attached.
Thanks!
> Should I push this commit myself, or let someone else do it?
>
If you have push
Alan Schmitt writes:
> Well, replacing "org-e-beamer-publish-to-latex" by
> "org-e-latex-publish-to-latex" results in the same error. I looked at
> the code, and my problem was that ":include" expects a list, so I'm able
> to make this .
I forgot one word: "work".
> I'll try to see if adding be
Suvayu Ali writes:
>> > That said, publishing is fully supported by the new exporter, just
>> > change the publishing function names to the functions provided by the
>> > new exporter.
>> >
>> > Here is an improperly tested example from one of my tests:
>> >
>> > (setq org-e-publish-project-alist
On Fri, Dec 07, 2012 at 05:12:46PM +0100, Alan Schmitt wrote:
> Suvayu Ali writes:
>
> > Since the new exporter is not documented yet, information is absent from
> > the info manual. You can find relevant docs in the source files. I am
> > slowly working towards a tutorial type docs for org-e-b
Suvayu Ali writes:
> Since the new exporter is not documented yet, information is absent from
> the info manual. You can find relevant docs in the source files. I am
> slowly working towards a tutorial type docs for org-e-beamer. When it
> is in shape, I'll push to Worg.
Great.
> That said,
On Fri, Dec 07, 2012 at 03:02:32PM +0100, Alan Schmitt wrote:
> Suvayu Ali writes:
>
> > You could try the publishing facilities in Org.
> >
> > (info "(org)Publishing")
>
> I did not know about that, it's a very nice suggestion. I have one
> question that I did not see addressed in the document
Suvayu Ali writes:
> You could try the publishing facilities in Org.
>
> (info "(org)Publishing")
I did not know about that, it's a very nice suggestion. I have one
question that I did not see addressed in the documentation, though: is
it possible to use it with the new exporter?
Thanks a lot,
On Fri, Dec 07, 2012 at 01:38:50PM +0100, Alan Schmitt wrote:
> Suvayu Ali writes:
>
> > On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote:
> >> Hello,
> >>
> >> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
> >> when I export it (either to beamer or to latex),
Suvayu Ali writes:
> On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote:
>> Hello,
>>
>> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
>> when I export it (either to beamer or to latex), it's using the name of
>> the file instead of the given file name.
>>
>> A
On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote:
> Hello,
>
> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
> when I export it (either to beamer or to latex), it's using the name of
> the file instead of the given file name.
>
> Am I doing something wrong here
Hello,
I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
when I export it (either to beamer or to latex), it's using the name of
the file instead of the given file name.
Am I doing something wrong here?
Thanks,
Alan
28 matches
Mail list logo
