Joseph Vidal-Rosset writes:
> How can I remove this old built-in Org "shadowed"
> by my new Elpa Org ? It seems to me that it should be the best
> solution,
That time I thought "life is too short to mess with it" :) and simply
ignored that zombie option; it's rare that an option is removed, so
Hello Andrea, thanks for your very useful reply and for the links.
2014-06-28 16:29 GMT+02:00 Andrea Rossetti :
> I had the same problem some time ago. That variable
> has been removed in recent Org versions, and you
> probably have (like me) an old built-in Org "shadowed"
> by a new Elpa Org. Yo
Joseph Vidal-Rosset writes:
> Hello,
> I meet problems to customize this variable via M-x customize-variable :
> Org Export Latex Hyperref Options Format
> I mean that the hypersetup options do not change in my .tex file after the
> export from an org-file.
>
> Does it correspond to a bug?
Hell
Hello,
I meet problems to customize this variable via M-x customize-variable :
Org Export Latex Hyperref Options Format
I mean that the hypersetup options do not change in my .tex file after the
export from an org-file.
Does it correspond to a bug?
If you know the solution, please, let me kno
t...@tsdye.com (Thomas S. Dye) writes:
> The template is set up to produce two pdf files, one with hyperref and
> the other without. I suspect this is the root of the problem I'm
> having.
Nope. The asynchronous process had to allow bind keywords.
All is well.
Tom
--
Thomas S. Dye
http://www
Aloha Nick,
Nick Dokos writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha Nick,
>>
>> Nick Dokos writes:
>>
>>> #+BIND is supposed to bind the variable *during export*. The test is to
>>> run the export and see if the hyperref stuff is gone from the tex file.
>>>
>>> Nick
>>
>> I did r
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha Nick,
>
> Nick Dokos writes:
>
>> #+BIND is supposed to bind the variable *during export*. The test is to
>> run the export and see if the hyperref stuff is gone from the tex file.
>>
>> Nick
>
> I did run the export and the hyperref stuff was still
Thomas,
Thomas S. Dye wrote:
Aloha Nick,
Nick Dokos writes:
#+BIND is supposed to bind the variable *during export*. The test is to
run the export and see if the hyperref stuff is gone from the tex file.
Nick
I did run the export and the hyperref stuff was still in the tex file.
I'm expo
Aloha Nick,
Nick Dokos writes:
> #+BIND is supposed to bind the variable *during export*. The test is to
> run the export and see if the hyperref stuff is gone from the tex file.
>
> Nick
I did run the export and the hyperref stuff was still in the tex file.
I'm exporting asynchronously--perha
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>>> If not, can someone offer advice on the best way to set
>>> org-latex-hyperref-template to achieve the same file-local effect?
>>
>> Assuming `org-export-allow-bind-keywords' is non-nil, does
>>
>> #+BIND: org-latex-hyperref
Nicolas Goaziou writes:
>> If not, can someone offer advice on the best way to set
>> org-latex-hyperref-template to achieve the same file-local effect?
>
> Assuming `org-export-allow-bind-keywords' is non-nil, does
>
> #+BIND: org-latex-hyperref-template ""
>
> work?
I can't get this to work.
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> It would be great if the texht option could still be supported.
The equivalent property is no longer a boolean. It can have complex
values, which cannot be set on the OPTIONS line.
> If not, can someone offer advice on the best way to set
> org-l
Thanks for the report. I'm not super familiar with how the texht option
works. I did made the following change base on recommendation from Nicolas
in the :options-alist.
(:latex-hyperref-p nil "texht" org-latex-with-hyperref t)
to
(:latex-hyperref nil nil org-latex-hyperref-template t)
>From Nico
Aloha all,
I noticed yesterday that a legacy document with this option:
#+OPTIONS: texht:nil
is now broken in a recent Org mode from master.
The following lines now appear in the LaTeX export, when they didn't before:
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 24.3.1 (O
Hi Nicolas,
Nicolas Goaziou writes:
> I think this patch is already in master.
Indeed, sorry for the noise,
PS: let's confirm on the list when a patch gets applied, that
helps archiving threads faster.
--
Bastien
Hello,
Bastien writes:
> can you repost the patch by creating another thread with [PATCH]
> in the subject line, and using plain text instead of HTML format?
>
> If you don't use plain text email, simply attach the patch instead
> of including it in the body of the email.
>
> Nicolas, I'll let y
Hi Joe,
Joe Hirn writes:
> Against the latest master:
can you repost the patch by creating another thread with [PATCH]
in the subject line, and using plain text instead of HTML format?
If you don't use plain text email, simply attach the patch instead
of including it in the body of the email.
Against the latest master:
**BEGIN PATCH*
>From 996e75b3538e60049645a5025a390be603425b8b Mon Sep 17 00:00:00 2001
From: Joe Hirn
Date: Mon, 24 Feb 2014 15:23:09 -0600
Subject: [PATCH] Allow customization of hyperrefsetup via
`org-latex-hyperref-template'
* ox-latex.el (o
Hi Joe,
Joe Hirn writes:
> Where can I clone the master branch from?
This should do the trick:
~$ git clone git://orgmode.org/org-mode.git
Best,
--
Bastien
Where can I clone the master branch from? I requested access to clone it
from the contribution page but was told that's reserved for frequent
committers. I generated this patch against the most recent version pulled
down from package.el (version 20140210).
On Sat, Feb 22, 2014 at 3:39 AM, Nicolas
Hello,
Joe Hirn writes:
> Here you go.
Thank you for the patch.
Unfortunately, I cannot apply it on master branch. Would you mind
updating your repository and generate the patch again?
Regards,
--
Nicolas Goaziou
Here you go.
Thanks a lot for all your help. Was really nice working on it with you.
>From af2a8066be01b94504fff9e009617ce186bd9e03 Mon Sep 17 00:00:00 2001
From: Joe Hirn
Date: Fri, 21 Feb 2014 12:15:58 -0600
Subject: [PATCH] Allow customization of hyperrefsetup via
`org-latex-hyperref-templa
Hello,
Joe Hirn writes:
> With recommended changes.
Thank you. It looks good.
Could you add a commit message (see "Commit messages and ChangeLog
entries" section in http://orgmode.org/worg/org-contribute.html) and
send it again, using "git format-patch"?
Regards,
--
Nicolas Goaziou
With recommended changes.
BEGIN PATCH *
diff --git a/ox-latex.el b/ox-latex.el
index 19f055e..f6e5a09 100644
--- a/ox-latex.el
+++ b/ox-latex.el
@@ -103,7 +103,7 @@
(:latex-class-options "LATEX_CLASS_OPTIONS" nil nil t)
(:latex-header "LATEX_HEADER" nil nil newline)
(:
I really appreciate your review. Sorry for the pedestrian code submission.
I don't get candid critical feedback on my e-lisp, so it's great to learn
more about its idioms and conventions.
I'll incorporate your feedback into a new patch.
On Thu, Feb 20, 2014 at 2:51 PM, Nicolas Goaziou wrote:
>
Hello,
Joe Hirn writes:
> I was able to test this on my local machine and it seems to work as we
> discussed.
>
> If there are any other changes to the patch you'd like to see, please let
> me know.
Thank you for the patch. Here are a few comments.
> - (:latex-hyperref-p nil "texht" org-late
Hi Nicholas.
I was able to test this on my local machine and it seems to work as we
discussed.
If there are any other changes to the patch you'd like to see, please let
me know.
Thanks for your help. I really appreciate it.
BEGIN PATCH**
diff --git a/ox-late
Ok. I was hesitant to require anything additional but I should be able
to knock this out.
Thx again.
Sent from my iPhone
> On Feb 20, 2014, at 4:22 AM, Nicolas Goaziou wrote:
>
> Hello,
>
> Joe Hirn writes:
>
>> Hi just sat down to code this up. I assume the keywords are so we can use
>> data
Hello,
Joe Hirn writes:
> Hi just sat down to code this up. I assume the keywords are so we can use
> data within the plist argument (info) passed to `org-latex-template'. But
> I'm not exactly sure what you mean by %k for keywords.
>
> Are you suggesting we could do something like:
>
> "\\hyper
Hi just sat down to code this up. I assume the keywords are so we can use
data within the plist argument (info) passed to `org-latex-template'. But
I'm not exactly sure what you mean by %k for keywords.
Are you suggesting we could do something like:
"\\hypersetup{\n pdfkeywords={%kkeywords},\n
I think that's a great idea.
Thanks for helping me workaround my individual problem and advice on what
type of patch you're welcoming.
I just happen to have the free time today so I'll try to get a patch to
you.
On Wed, Feb 19, 2014 at 7:05 AM, Nicolas Goaziou wrote:
> Hello,
>
> Joe Hirn wri
Hello,
Joe Hirn writes:
> So I understand, you're recommending I disable org-latex-with-hyperref and
> then add my own \\hypersetup. My goal would be to avoid placing a #+ entry
> into every .org file I compose. Which var would be the easiest to to adjust
> so I can emit \\hypersetup by default
I'm sorry man. That may have came off wrong. Did not mean to sound
ungrateful.
Thanks for offering the workarounds and thanks for responding.
I definitely agree with drawback #2.
So I understand, you're recommending I disable org-latex-with-hyperref and
then add my own \\hypersetup. My goal woul
Joe Hirn writes:
> Hm. That's disappointing. I really prefer the original behavior. I don't
> want to copy #+latex_header to get this default behavior into each of my
> org-mode files.
>
> I guess I'll just have to maintain this by redefining the entire
> org-latex-template function to look at my
Joe Hirn writes:
> Hm. That's disappointing. I really prefer the original behavior. I don't
> want to copy #+latex_header to get this default behavior into each of my
> org-mode files.
I suggested other ways to handle it.
Anyway your patch has two drawbacks:
1. It is partly redundant with `o
Hm. That's disappointing. I really prefer the original behavior. I don't
want to copy #+latex_header to get this default behavior into each of my
org-mode files.
I guess I'll just have to maintain this by redefining the entire
org-latex-template function to look at my variable instead of the hard
Hello,
Joe Hirn writes:
> Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs
> 24.3 and lost the ability to customize the \hypersetup block via the custom
> var org-export-latex-hyperref-options-format. Platform is OSX, Emacs
> installed via homebrew and org-mode updated via
Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs
24.3 and lost the ability to customize the \hypersetup block via the custom
var org-export-latex-hyperref-options-format. Platform is OSX, Emacs
installed via homebrew and org-mode updated via package.el.
Org 7.x defines the v
38 matches
Mail list logo
