Re: [O] How do I automatically run a function whenever an org file is loaded?
Herbert Sitz nwlink.com> writes: > > I'd like to put a function in my .emacs file to run each time an org file is > loaded. > > I don't see any hook for this among org-mode hooks; I assume this is something > that's accomplished using generic Emacs. > > Can someone tell me how to set this up? > Sorry for the trouble, I think it is indeed one of the org-mode hooks, specifically 'org-mode-hook'. -- Herb
[O] How do I automatically run a function whenever an org file is loaded?
I'd like to put a function in my .emacs file to run each time an org file is loaded. I don't see any hook for this among org-mode hooks; I assume this is something that's accomplished using generic Emacs. Can someone tell me how to set this up? Thanks, Herb
Re: [O] The Orgfather
Very cute. A few random thoughts: (1) You'll be hearing from the studio's lawyers first thing Monday morning. (2) Is that horse flesh I smell in your bedroom? (3) Is somebody going to add a "vimeo" export mode to Org? -- Mike > >From: Bastien >To: emacs-orgmode@gnu.org >Sent: Saturday, August 27, 2011 8:05 AM >Subject: [O] The Orgfather > >Hi folks, > >http://lumiere.ens.fr/~guerry/theorgfather.html > >Enjoy! > >-- >Bastien > > > >
Re: [O] [odt] equation labels
Myles
> Does anyone know how to cause a label such as "Figure 1." in the odt
> (for the resulting png), and set the caption for an equation such as:
>
> #+CAPTION: some caption
> #+LABEL: eqn:psychrometric
> \begin{equation*}
> \label{eq:psychrometric}
> \capillaryPressure = ln(RH)\cdot \dens_w\frac{RT}{M_w}
> \end{equation*}
>
> ?
>
> The orgmode manual says that captions and labels are for images and
> tables so unless there is a special trick I would probably try to wrap
> the latex in something first, for dvipng to return the png to org, to
> apply the CAPTION to, before exporting to odt.
>
> Extra points for making it "Equation 1." instead of "Figure 1.".
I have added support for honoring captions, label and attributes for
images that are dervied from latex fragments. Checkout the git repo and
let me know if there are any rough edges that need to be ironed out.
Note that the odt exporter treats Labels and their references in a
special way.
For example, if the label is defined as follows,
#+LABEL: Equation:1
Equation is considered as a "Category" [1] and "1" is considered as
sequence number. So this "category:seq-no" is the recommended form of
labels for odt export. Note that the seq-no found in Org file need not
be sequential. The odt exporter will faithfully reproduce the seqnos as
seen Org file to the odt file. You can auto-generate the "right" seqnos
by using Tools->Update->Update All.
If you are averse to launching the gui for updating of indices you can
do a odt->odt (yes, odt->odt) conversion for sanitizing of indices [2].
It is also worth noting that the attached file uses the as yet
undocumented
#+ATTR_ODT: (:scale 2)
to scale the image to twice the original size.
Jambunathan K.
> Thanks,
>
> Myles
>
>
Footnotes:
[1] Other "Categories" could be Illustration, Table, Text etc.
[2] I have never used unoconv myself. But the source code does update
indices of the input document before further conversion.
--
#+TITLE: eqns.org
#+AUTHOR:Jambunathan K
#+EMAIL: kjambunat...@gmail.com
#+DATE: 2011-08-26 Fri
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:dvipng skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
* Equations
There is a equation down below.
#+CAPTION: Kinetic Energy
#+LABEL: Equation:1
#+ATTR_ODT: (:scale 2)
\begin{equation*}
e = \frac{1}{2}mv^2
\end{equation*}
#+CAPTION: Kinetic Energy
#+LABEL: Equation:2
#+ATTR_ODT: (:scale 0.5)
\begin{equation*}
e = \frac{1}{2}mv^2
\end{equation*}
eqns.odt
Description: eqns.odt
Re: [O] biblatex citation
Nicolas Goaziou writes:
> Hello,
>
> Nick Dokos writes:
>
>> Nick Dokos wrote:
>>
>>> Thomas S. Dye wrote:
>>>
>>> > Aloha all,
>>> >
>>> > This biblatex construct:
>>> > \parencites[234]{kirch85}[185]{kirch84}
>>> >
>>> > is output like this:
>>> > \parencites[234]{kirch85}[185]\{kirch84\}
>>> >
>>> > The biblatex syntax is unusual (to me) in LaTeX. I wonder if it is
>>> > possible to support it in Org-mode?
>>> >
>>>
>>> So is the syntax \parencites followed by an arbitrary number of pairs
>>> [page#]{ref}?
>>>
>>> latex export knows to do the right thing for a command with optional and
>>> mandatory arguments: \command[opt]{mand} is properly protected, but the
>>> above case stretches it to beyond its breaking point.
>>>
>>> After a quick look, all I could come up with as a possibility was yet
>>> another special case in org-export-latex-preprocess - and one more scan
>>> of the whole file to add to the many (roughly 20!) that this function
>>> does.
>>>
>>
>> Well, maybe another scan is not necessary: the existing command handler
>> could perhaps be extended to deal with this case. But the regexp in
>> that case is horrendous enough as it is - if it gets any hairier, it
>> will become Medusa: mortals looking at it will drop dead.
>> However it might be that a loop that eats multiple pairs of [...]{...}
>> occurrences would be simple enough to implement.
>
> Note that Org core already recognizes such latex commands, as confirmed
> by using `org-inside-latex-macro-p' anywhere inside it.
>
> In this case, it's just an exporter failure.
>
> Regards,
Aloha Nick and Nicolas,
Thanks for analyzing this problem.
Yes, the syntax of \parencites (and various other "multicite" commands
in biblatex) allows an arbitrary number of [][]{}
triplets. I haven't seen this before in LaTeX. The biblatex author,
Philipp Lehman, came up with this to solve a long-standing problem in
BibTeX citations where it was possible to cite multiple works in one
citation, but impossible then to indicate page numbers, etc., for
individual works.
The solutions you've pointed out, a pre-process hook or correcting an
exporter failure, both seem beyond me to implement and/or maintain. In
the meantime, I came up with a workaround that seems to work. It looks
like this in the Org-mode buffer:
\parencites[[multicite:][;]][[multicite:][;]]
It is based on this custom link, which integrates with ebib:
#+source: define-biblatex-multicite-link
#+begin_src emacs-lisp :results silent :exports none
(org-add-link-type
"multicite" 'ebib
(lambda (path desc format)
(cond
((eq format 'html)
(format "(%s)" path))
((eq format 'latex)
(if (or (not desc) (equal 0 (search "multicite:" desc)))
(format "{%s}" path)
(format "[%s][%s]{%s}"
(cadr (split-string desc ";"))
(car (split-string desc ";")) path))
#+end_src
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
[O] Library of Babel function
Hi Eric,
The booktabs-notes function, below, is based on the booktabs function in
the library of Babel. It takes a second table and adds it to the bottom
of the main table. I use it to add multicolumn footnotes to the bottom
of the table. There is also a switch that adds a linespace between the
main table and the notes table. I think the function might be a useful
addition to the library of Babel.
I tried to design it to be a functional replacement for the booktabs
function, but don't trust my emacs-lisp (or other) programming skills.
All the best,
Tom
#+srcname: booktabs-notes
#+begin_src emacs-lisp :var table='((:head) hline (:body)) :var notes='() :var
align='() :var env="tabular" :var width='() :var lspace='() :noweb yes :results
latex
(flet ((to-tab (tab)
(orgtbl-to-generic
(mapcar (lambda (lis)
(if (listp lis)
(mapcar (lambda (el)
(if (stringp el)
el
(format "%S" el))) lis)
lis)) tab)
(list :lend " " :sep " & " :hline "\\hline"
(org-fill-template
"
\\begin{%env}%width%align
\\toprule
%table
\\bottomrule%spacer
%notes
\\end{%env}\n"
(list
(cons "env" (or env "table"))
(cons "width" (if width (format "{%s}" width) ""))
(cons "align" (if align (format "{%s}" align) ""))
(cons "spacer"(if lspace "\\addlinespace" ""))
(cons "table"
;; only use \midrule if it looks like there are column headers
(if (equal 'hline (second table))
(concat (to-tab (list (first table)))
"\n\\midrule\n"
(to-tab (cddr table)))
(to-tab table)))
(cons "notes" (if notes (to-tab notes) ""))
)))
#+end_src
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] How to reuse page keywords for LaTeX with pdfkeywords and hyperref package?
In case someone else also wants page keywords to appear in latex export.
Here is the link to original thread
http://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg01429.html .
There is a patch at the bottom that does that. It assumes that hyperred
package is used and doesn't check that!
I'm not sure if I'm doing it right as I don't know lisp and emacs much.
Mikhail
>From ee027f75db3df6b16ccb2e8f96916fe7274655f3 Mon Sep 17 00:00:00 2001
From: Mikhail Titov
Date: Sat, 27 Aug 2011 11:59:06 -0500
Subject: [PATCH] Set keywords and subject fields in pdf
---
lisp/org-latex.el | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 17626b5..4c35528 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1391,6 +1391,10 @@ OPT-PLIST is the options plist for current buffer."
(let ((toc (plist-get opt-plist :table-of-contents))
(author (org-export-apply-macros-in-string
(plist-get opt-plist :author)))
+(description (org-export-apply-macros-in-string
+ (plist-get opt-plist :description)))
+(keywords (org-export-apply-macros-in-string
+ (plist-get opt-plist :keywords)))
(email (replace-regexp-in-string
"_" "_"
(org-export-apply-macros-in-string
@@ -1428,6 +1432,15 @@ OPT-PLIST is the options plist for current buffer."
(format-time-string
(or (plist-get opt-plist :date)
org-export-latex-date-format)))
+ ;; add pdf things
+ "\\hypersetup{\n"
+ ;; " pdfinfo={\n"
+ (format " pdfkeywords={%s},\n"
+ (org-export-latex-fontify-headline keywords))
+ (format " pdfsubject={%s}\n"
+ (org-export-latex-fontify-headline description))
+ ;;" }\n"
+ "}\n"
;; beginning of the document
"\n\\begin{document}\n\n"
;; insert the title command
--
1.7.4.1
Re: [O] How can I bypass the agenda dispatcher and call a custom block agenda directly?
Pieter Praet praet.org> writes: > That's because you need to wrap it in a lambda function. Okay, thanks. Ciao, Marcus
Re: [O] Convert list to paragraph
Derek Thomas wrote:
> > Nick Dokos writes:
> >
> >> (defun org-list-to-paragraph ()
> >> "Convert the list at point into a paragraph."
> >> (interactive)
> >> (insert (org-list-to-generic (org-list-parse-list t)
> >> '(:ustart ""
> >> :splice t
> >> :isep " "
> >> :nobr t
> >>
> >>
> >> (defun org-lists-to-paragraphs ()
> >> (goto-char (point-min))
> >> (condition-case nil
> >>(while (org-list-search-forward "+ ")
> >> (org-list-to-paragraph))
> >> (error nil)))
> >>
> >> (add-hook 'org-export-preprocess-hook
> >>(function org-lists-to-paragraphs))
>
>
> This looks like it will do what I want. Is there any way to restrict
> this export option to certain org files? Thanks,
>
With elisp you can do anything: just a small matter of
programming (TM). E.g. you can set up a list with the
files that you want this to apply to and then check in
org-lists-to-paragraphs whether the file you are
exporting is in the list: if not, don't do
anything. Here's a quick and rather dirty
implementation - a minor variation on the above:
(setq ndk-list-to-paragraph-file-list '("/home/nick/src/org/list/to-paragraph/derek-thomas.org"))
(defun org-list-to-paragraph ()
"Convert the list at point into a paragraph."
(interactive)
(insert (org-list-to-generic (org-list-parse-list t) '(:ustart "" :splice t :isep " " :nobr t
(defun ndk-buffer-file-name ()
;;; if called from inside org-export-preprocess-string
;;; source-buffer will be bound to the original org buffer, not the temp buffer
;;; otherwise assume we want to operate on the current buffer
;;; don't bother telling me how ugly this is - I know
;;; but do bother telling me about a better way to do it.
(if (boundp 'source-buffer)
(buffer-file-name source-buffer)
(buffer-file-name (current-buffer
(defun org-lists-to-paragraphs ()
(if (not (member (ndk-buffer-file-name) ndk-list-to-paragraph-file-list))
nil
(goto-char (point-min))
(condition-case nil
(while (org-list-search-forward "+ ")
(org-list-to-paragraph))
(error nil
(add-hook 'org-export-preprocess-hook (function org-lists-to-paragraphs))
but depending on your needs, you might want to do it
differently. It is just a matter of figuring out what
criteria you want to apply and then figuring out how
to implement those criteria.
Nick
PS Is there a better way to get the original buffer
name?
Re: [O] disable "org-decrypt: auto-save-mode may cause leakage"
On Tue, 19 Jul 2011 01:12:23 +0200, Bastien wrote: > Hi Sébastien, > > "Sebastien Vauban" writes: > > > I simply call C-c C-x C-j to jump to the current clocking entry, and the > > question "org-decrypt: auto-save-mode may cause leakage. Disable it for > > current buffer? (y or n)" pops up -- while the current buffer has nothing > > special, as said above. > > Weird. > > Maybe you have some hook in `org-clock-goto-hook' that makes Org visit > some buffer containing encrypted entries? Apparently not config-related. I don't use org-clock.el (and as such don't have any org-clock related config, `org-clock-goto-hook' is nil), but due to a recent freak accident involving spastic typing, I've managed to trigger the issue. Apologies for dismissing it earlier, Sebastien. `org-clock-goto' erroneously causes `org-decrypt-entry' to be called, though it's not immediately obvious how or why this would happen. Maybe Carsten (being listed as sole author for org-clock.el) can provide some insight? > -- > Bastien > Peace -- Pieter
Re: [O] The Orgfather
I am experiencing *so* much cognitive dissonance right now. -deech On Sat, Aug 27, 2011 at 10:46 AM, suvayu ali wrote: > On Sat, Aug 27, 2011 at 5:05 PM, Bastien wrote: > > Hi folks, > > > > http://lumiere.ens.fr/~guerry/theorgfather.html > > > > Enjoy! > > Ignoring the Hindi audio was a bit difficult for me. :D :D > > > -- > Suvayu > > Open source is the future. It sets us free. > >
Re: [O] The Orgfather
On Sat, Aug 27, 2011 at 5:05 PM, Bastien wrote: > Hi folks, > > http://lumiere.ens.fr/~guerry/theorgfather.html > > Enjoy! Ignoring the Hindi audio was a bit difficult for me. :D :D -- Suvayu Open source is the future. It sets us free.
Re: [O] Merge org-7.7 into emacs
On Mon, 15 Aug 2011 16:39:44 +0200, Bastien wrote: > Hi Memnon, > > Memnon Anon writes: > > >http://permalink.gmane.org/gmane.emacs.devel/142944 > > > > I don't know anything about this, but maybe something can be said/done > > about it while Bastien enjoys his vacation? > > Thanks for the heads-up -- I just answered to Glenn and fixed the more > obvious problems. I'm now waiting Achim's and Pieter's answers about > their copyright status wrt FSF. > > Best, > > -- > Bastien > Apologies for being so late to the party. The weather was/is simply too good :) I've submitted the assignment form request a few days ago, but have yet to receive confirmation of any sort or form. Will keep you posted. Peace -- Pieter
Re: [O] How can I bypass the agenda dispatcher and call a custom block agenda directly?
On Sat, 27 Aug 2011 13:45:26 + (UTC), Marcus Klemm wrote: > Bernt Hansen norang.ca> writes: > > > > Certainly this is doable > > > > (org-agenda t "a") > > > > Just bind this to the key of your choice and substitute "a" with the > > agenda you want to run. > > Doesn't work for me. I get: > > recursive-edit: Wrong type argument: commandp, (org-agenda t "A") > > That's because you need to wrap it in a lambda function. This should work: #+begin_src emacs-lisp (global-set-key (kbd " a") '(lambda () (interactive) (org-agenda t "a"))) #+end_src Peace -- Pieter
[O] The Orgfather
Hi folks, http://lumiere.ens.fr/~guerry/theorgfather.html Enjoy! -- Bastien
Re: [O] Convert list to paragraph
> Nick Dokos writes: > >> (defun org-list-to-paragraph () >> "Convert the list at point into a paragraph." >> (interactive) >> (insert (org-list-to-generic (org-list-parse-list t) '(:ustart "" :splice >> t :isep " " :nobr t >> >> >> (defun org-lists-to-paragraphs () >> (goto-char (point-min)) >> (condition-case nil >> (while (org-list-search-forward "+ ") >> (org-list-to-paragraph)) >> (error nil))) >> >> (add-hook 'org-export-preprocess-hook (function org-lists-to-paragraphs)) This looks like it will do what I want. Is there any way to restrict this export option to certain org files? Thanks, Derek
Re: [O] How can I bypass the agenda dispatcher and call a custom block agenda directly?
Bernt Hansen norang.ca> writes: > Certainly this is doable > > (org-agenda t "a") > > Just bind this to the key of your choice and substitute "a" with the > agenda you want to run. Doesn't work for me. I get: recursive-edit: Wrong type argument: commandp, (org-agenda t "A")
Re: [O] Footnotes and Tufte-Latex
Hi Aditya,
On Thu, Aug 25, 2011 at 4:55 PM, Aditya Mandayam wrote:
> This would mean conditional export to HTML and Latex. How can this be done?
>
What do you mean by conditional export? Are you talking about
\cite{..} macros being translated to footnotes for html export, or
something else like custom CSS styles?
As always an ECM (Minimal Complete Example) helps everyone follow what
you are trying and what you expect much better.
--
Suvayu
Open source is the future. It sets us free.
[O] Exporting visible tree doesn't respect file local variables
Hi everyone,
I think I found a bug. When exporting the visible outlines (say after a
sparse tree search) file local variables are ignored.
To give you an example, in the attached org file I use file local
variables to setup latex export to use xelatex by customising
org-latex-to-pdf-process. For regular pdf export (C-c C-e p) xelatex is
run. However when I export the visible trees (C-c C-e v p) after a
sparse tree search (say the tag Qn in my example), pdf export uses
pdflatex disregarding the file local variable.
This happens with other file local variables too, I chose this one as it
was easier for me construct an example. I hope I have given enough
details to debug the issue.
Thanks,
--
Suvayu
Open source is the future. It sets us free.
#+TITLE: Analysis
#+AUTHOR:
#+EMAIL:
#+DATE:
#+LANGUAGE: en
#+OPTIONS: H:3 num:nil toc:t \n:nil @:nil ::t |:t ^:t -:t f:t *:t <:nil
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil
* Bs decay (Bs->Dsh)
Bs->DsK or Dsπ
** Decay model :Qn:
1. Justify neglecting CP violation
2. Verify master equations
** Detector effects :Qn:
1. How is the Gaussian used for smearing of proper time resolution
derived?
2. Why is the per event proper time error PDF needed? Why is smearing
of time resolution not enough?
# Local Variables:
# org-latex-to-pdf-process: ("xelatex -interaction nonstopmode
-output-directory %o %f" "xelatex -interaction nonstopmode -output-directory %o
%f" "xelatex -interaction nonstopmode -output-directory %o %f")
# End:
Re: [O] a new way to navigate your org files
I just found this and it's great -- thanks! On Mon, Apr 25, 2011 at 2:25 PM, Tom wrote: > Suvayu Ali gmail.com> writes: >> >> This is very useful. I made some enhancements in the attached patches. >> The first one adds a very basic minibuffer history. You can navigate the >> history by the usual `M-p' and `M-n'. The second patch fixes an issue, >> now you can go to the first match by just hitting `RET' instead of >> ` RET'. >> > > I added your changes to the code (implementing the second one slightly > differently, but it works the same way). > > I also turned on full cursor for the Occur buffer, instead of the hollow > one, so it can be seen more easily. > > The code is on EmacsWiki for easier downloed: > > http://www.emacswiki.org/emacs/org-occur-goto.el > > > >
Re: [O] How can I bypass the agenda dispatcher and call a custom block agenda directly?
Marcus Klemm writes: > I almost exclusively use a custom block agenda and want to bind it to > a key instead of going through the agenda dispatcher. Is that > possible? Hi Marcus, Certainly this is doable (org-agenda t "a") Just bind this to the key of your choice and substitute "a" with the agenda you want to run. Regards, Bernt
Re: [O] Problem with exporting image to PDF
Hi Tom, Nick, and suvayu, Thank you for your replies, I really appreciate the warm welcome! Good news is, I got it working using PNG images... Slightly bad news is I don't actually know how :-) It seems like just posting to the list made it magically work. Actually, I have tried several times to replicate it *not* working without success, so was probably my own error in listing the right file path/name. Tom, I have discovered the Org-mode version I have is behind-the-times (7.01g on Debian Squeeze). Thank you for your suggestions on ECM which I shall know to use next time I post. Cheers, Toby -Original Message Date: Thu, 25 Aug 2011 10:23:02 -0400 From: Nick Dokos To: suvayu ali Cc: "Thomas S. Dye" , emacs-orgmode@gnu.org,Toby , nicholas.do...@hp.com Subject: Re: [O] Problem with exporting image to PDF suvayu ali wrote: > Hi Toby, John and Nick, > > Its early in the morning for me, so whatever follows could simply be > wrong. :-p > > On Thu, Aug 25, 2011 at 3:59 AM, Nick Dokos wrote: > > Thomas S. Dye wrote: > > > >> Toby writes: > >> > >> > I have tried different classes (article and koma-article) such as: ^^^ > >> > #+LaTeX_CLASS: koma-article > >> > #+LaTeX_CLASS_OPTIONS: [a4paper] > >> > > > I believe this might be your problem. Org recognises only a few document > classes by default. You need to add to the org-export-latex-classes > variable to support other classes. Presently the supported classes are: > article, report, book and beamer. > The OP tried article - see above. > >> > >> Out of the box, Org-mode uses pdflatex to create pdf from LaTeX source > >> (although this can be modified). Pdflatex does not accept eps files for > >> graphic input, so this might have been part of your problem. It does > >> accept png files, though, so it appears something else might be going > >> on. > >> > > > > It's probably the case that even though there is a processing error with > > .eps files, in some circumstances, a PDF file *is* produced, but it's > > just a skeleton and therefore does not properly render even the "good" > > image. If the OP deletes the .eps lines, the .png one will probably > > work. > > > > Actually for TeXLive 2010 and above all included eps files are converted > to pdf (with eps2pdf I think) and included. I am not sure if this is the > case for earlier versions though. > Not sure what version I have, but it does throw an error w/eps. I'll see if I can upgrade. Thanks, Nick > HTH > > -- > Suvayu > > Open source is the future. It sets us free. >
[O] How can I bypass the agenda dispatcher and call a custom block agenda directly?
Hello List, I almost exclusively use a custom block agenda and want to bind it to a key instead of going through the agenda dispatcher. Is that possible? Ciao, Marcus
Re: [O] Bug: failed latex-export [7.7]
Oliver Gerlach writes: > I expect a complete tex file without this bug message: > >> Export buffer: >> Exporting to LaTeX... >> org-export-latex-subcontent: Symbol's function definition is void: nil >> Auto-saving... >> Mark set > > Do you have some suggestions what to do? I cannot reproduce this. Since I don't think that version 7.7 comes with your version of emacs, you might be picking up an older version of org-install or otherwise having a mix of an older vs. newer Org version. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] git diff: hunk header config
Michael Brand writes: > Thanks for the clarification. Because I didn't expect this at all it > took me some time to understand that a local config affects also the > diffs already committed, not only "git diff" of uncommitted changes. Git doesn't "commit diffs", which is why this is working (and a frequent source of confusion for people who don't know the architecture of Git). > Neat. One of those things that reassures me that Git has made the right choices. > But aren't there still things lost when one does this only locally? > 1) The web browser view of the git repos >http://orgmode.org/w/org-mode.git, its delayed mirror >http://repo.or.cz/w/org-mode.git and http://repo.or.cz/w/Worg.git >(for code/elisp/): Can be solved by configuring these three >repos locally. I wouldn't know how to configure repo.or.cz (or any other mirror), but it might be worth asking the maintainers of that site if they would consider adding a global configuration. Customizing the (global) configuation on orgmode.org is at Jasons discretion, I guess. > 2) When reading patches submitted to the mailing list: Here I don't >know the solution. In my simple trial, .gitattributes was not >available in its clone done afterwards. Don't read them on the mailing list, then. Apply them in Git and look at them whichever way you want to. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] biblatex citation
Hello,
Nick Dokos writes:
> Nick Dokos wrote:
>
>> Thomas S. Dye wrote:
>>
>> > Aloha all,
>> >
>> > This biblatex construct:
>> > \parencites[234]{kirch85}[185]{kirch84}
>> >
>> > is output like this:
>> > \parencites[234]{kirch85}[185]\{kirch84\}
>> >
>> > The biblatex syntax is unusual (to me) in LaTeX. I wonder if it is
>> > possible to support it in Org-mode?
>> >
>>
>> So is the syntax \parencites followed by an arbitrary number of pairs
>> [page#]{ref}?
>>
>> latex export knows to do the right thing for a command with optional and
>> mandatory arguments: \command[opt]{mand} is properly protected, but the
>> above case stretches it to beyond its breaking point.
>>
>> After a quick look, all I could come up with as a possibility was yet
>> another special case in org-export-latex-preprocess - and one more scan
>> of the whole file to add to the many (roughly 20!) that this function
>> does.
>>
>
> Well, maybe another scan is not necessary: the existing command handler
> could perhaps be extended to deal with this case. But the regexp in
> that case is horrendous enough as it is - if it gets any hairier, it
> will become Medusa: mortals looking at it will drop dead.
> However it might be that a loop that eats multiple pairs of [...]{...}
> occurrences would be simple enough to implement.
Note that Org core already recognizes such latex commands, as confirmed
by using `org-inside-latex-macro-p' anywhere inside it.
In this case, it's just an exporter failure.
Regards,
--
Nicolas Goaziou
Re: [O] git diff: hunk header config
Hi Achim, Jason and Matt On Wed, Aug 24, 2011 at 21:37, Achim Gratz wrote: > Michael Brand writes: >> For .git/config I am not sure if it can be made a versioned git repo >> element. If not, I don't know how it can become part of the transfer >> during git pull which it should be in any case. Proposal for the >> content (changed from first post): > > You can't and I don't think that is an oversight. As a general > principle such configurations should not be part of the repository at > all. Please note that if you do configure it that way locally, all > tools in git will show all diffs in the new format, so there is nothing > lost if everybody doesn't have the same configuration. Thanks for the clarification. Because I didn't expect this at all it took me some time to understand that a local config affects also the diffs already committed, not only "git diff" of uncommitted changes. Neat. But aren't there still things lost when one does this only locally? 1) The web browser view of the git repos http://orgmode.org/w/org-mode.git, its delayed mirror http://repo.or.cz/w/org-mode.git and http://repo.or.cz/w/Worg.git (for code/elisp/): Can be solved by configuring these three repos locally. 2) When reading patches submitted to the mailing list: Here I don't know the solution. In my simple trial, .gitattributes was not available in its clone done afterwards. @Jason and Matt: At least, changing 1) alone would already help. What do you think? Michael
[O] Bug: failed latex-export [7.7]
Dealing with current org installations I found out that latex export is
in general not working (command =C-C C-E l=)
The generated tex file stops at the beginning, here an example:
Created 2011-08-26 Fri 14:40
\documentclass[11pt,a4paper]{article}
\usepackage[AUTO]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\title{Title}
\author{Oliver Gerlach}
\date{\today}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
I expect a complete tex file without this bug message:
Export buffer:
Exporting to LaTeX...
org-export-latex-subcontent: Symbol's function definition is void: nil
Auto-saving...
Mark set
Do you have some suggestions what to do?
Regards
Oliver Gerlach
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.35)
of 2011-03-10 on black.porkrind.org
Package: Org-mode version 7.7
current state:
==
(setq
org-property-format "%-18s %s"
org-export-with-LaTeX-fragments 'mathjax
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-files
'("~/Documents/Oliver/Kongresse/Thessaloniki/essay/bari.org")
org-metaup-hook '(org-babel-load-in-session-maybe)
org-startup-truncated nil
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-startup-folded nil
org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-support-shift-select 'always
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-blank-before-new-entry nil
org-babel-pre-tangle-hook '(save-buffer)
org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-hide-drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-export-latex-classes '(("article"
"\\documentclass[11pt,a4paper]{article}")
("report"
"\\documentclass[11pt,a4paper]{report}\n\\usepackage[utf8]{inputenc}\n\\usepackage[T1]{fontenc}\n\\usepackage{graphicx}\n\\usepackage{longtable}\n\\usepackage{float}\n\\usepackage{wrapfig}\n\\usepackage{soul}\n\\usepackage{amssymb}\n\\usepackage{hyperref}"
("\\part{%s}" . "\\part*{%s}") ("\\chapter{%s}" .
"\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}") ("\\subsection{%s}" .
"\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
("book"
"\\documentclass[11pt,a4paper,twoside]{article}\n\\usepackage[utf8]{inputenc}\n\\usepackage[T1]{fontenc}\n\\usepackage{graphicx}\n\\usepackage{longtable}\n\\usepackage{float}\n\\usepackage{wrapfig}\n\\usepackage{soul}\n\\usepackage{amssymb}\n\\usepackage{hyperref}\n\\usepackage[round]{natbib}"
("\\part{%s}" . "\\part*{%s}") ("\\chapter{%s}" .
"\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}") ("\\subsection{%s}" .
"\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
)
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-mode-hook '(#[nil "\300\301\302\303\304$\207" [org-add-hook
change-major-mode-hook org-show-block-all append local] 5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-babel-show-result-all
append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes
turn-on-org-cdlatex)
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-export-interblocks '((lob org-babel-exp-lob-one-liners) (src
org-babel-exp-inline-src-blocks))
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-occur-hook '(org-first-headline-recenter)
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-export-latex-final-
Re: [O] biblatex citation
Nick Dokos wrote:
> Thomas S. Dye wrote:
>
> > Aloha all,
> >
> > This biblatex construct:
> > \parencites[234]{kirch85}[185]{kirch84}
> >
> > is output like this:
> > \parencites[234]{kirch85}[185]\{kirch84\}
> >
> > The biblatex syntax is unusual (to me) in LaTeX. I wonder if it is
> > possible to support it in Org-mode?
> >
>
> So is the syntax \parencites followed by an arbitrary number of pairs
> [page#]{ref}?
>
> latex export knows to do the right thing for a command with optional and
> mandatory arguments: \command[opt]{mand} is properly protected, but the
> above case stretches it to beyond its breaking point.
>
> After a quick look, all I could come up with as a possibility was yet
> another special case in org-export-latex-preprocess - and one more scan
> of the whole file to add to the many (roughly 20!) that this function
> does.
>
Well, maybe another scan is not necessary: the existing command handler
could perhaps be extended to deal with this case. But the regexp in
that case is horrendous enough as it is - if it gets any hairier, it
will become Medusa: mortals looking at it will drop dead.
However it might be that a loop that eats multiple pairs of [...]{...}
occurrences would be simple enough to implement.
My preferred solution would be for \parencites to change its syntax :-)
If it were implemented like this e.g.
\parencites{234|kirch85|185|kirch84}
it would be easier to type *and* org would be able to handle it
out of the box: a win-win for everybody except for the parencites
author.
Nick
Re: [O] biblatex citation
Thomas S. Dye wrote:
> Aloha all,
>
> This biblatex construct:
> \parencites[234]{kirch85}[185]{kirch84}
>
> is output like this:
> \parencites[234]{kirch85}[185]\{kirch84\}
>
> The biblatex syntax is unusual (to me) in LaTeX. I wonder if it is
> possible to support it in Org-mode?
>
So is the syntax \parencites followed by an arbitrary number of pairs
[page#]{ref}?
latex export knows to do the right thing for a command with optional and
mandatory arguments: \command[opt]{mand} is properly protected, but the
above case stretches it to beyond its breaking point.
After a quick look, all I could come up with as a possibility was yet
another special case in org-export-latex-preprocess - and one more scan
of the whole file to add to the many (roughly 20!) that this function
does.
Nick
[O] biblatex citation
Aloha all,
This biblatex construct:
\parencites[234]{kirch85}[185]{kirch84}
is output like this:
\parencites[234]{kirch85}[185]\{kirch84\}
The biblatex syntax is unusual (to me) in LaTeX. I wonder if it is
possible to support it in Org-mode?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
