Re: [Orgmode] contrib/README
Am 01.07.2010 11:07, schrieb Carsten Dominik: > > On Jul 1, 2010, at 11:01 AM, Stephen Eglen wrote: >> - how do I query git to find out where this file has gone? > > This one was removed because its functionality is included in Org babel. > Files added and removed are usually listed in the list of user visible > changes. > I am not sure how to find it in git. Should be possible with git grep or git bisect. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] contrib/README
Am 01.07.2010 11:07, schrieb Carsten Dominik: > > On Jul 1, 2010, at 11:01 AM, Stephen Eglen wrote: >> - how do I query git to find out where this file has gone? > > This one was removed because its functionality is included in Org babel. > Files added and removed are usually listed in the list of user visible > changes. > I am not sure how to find it in git. Should be possible with git grep or git bisect. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Co-maintainer, a least for some time?
Hi, Am 19.05.2010 17:46, schrieb Carsten Dominik: > I think an issue-tracking system would be great. And if there are > other people besides John who want to take up individual issues, I am > sure this would be good. One solution would be to switch the git repository to github.com and use it's integrates issues functionality. From their site: Issues GitHub Issues adds lightweight issue tracking tightly integrated with your repository. Close issues from commit messages, let users label and vote on issues and drag & drop issues to priorize. See it in action at http://github.com/splitbrain/dokuwiki-plugin-data/issues Maybe it's worth a look. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-clock-goto plus org-narrow-to-subtree?
Hi Carsten, Carsten Dominik writes: > On Apr 12, 2010, at 3:05 PM, Karsten Heymann wrote: >> does anyone have a solution to combine org-clock-goto with >> org-narrow-to-subtree, so that upon keypress I get a buffer with only >> the currently clocked task in it? Maybe this could even become a >> optional parameter for org-clock-goto? > > (defun my-clock-goto-narrow () >(interactive) >(when (org-clock-is-active) > (org-clock-goto) > (org-narrow-to-subtree))) > > (define-key global-map "\C-cc" my-clock-goto-narrow) Thanks, applied. :-) Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] org-clock-goto plus org-narrow-to-subtree?
Hi, does anyone have a solution to combine org-clock-goto with org-narrow-to-subtree, so that upon keypress I get a buffer with only the currently clocked task in it? Maybe this could even become a optional parameter for org-clock-goto? Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Hi, Ulf Stegemann writes: > But if that wasn't your point, just forget about my remark. Done :-) Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Hi Carsten, Carsten Dominik writes: > On Apr 7, 2010, at 10:22 AM, Karsten Heymann wrote: >> But chances are high that most "normal" LaTeX documents will not work >> with xelatex anyways due to encoding or font selection issues, so I >> think unless org-mode aims at explicitely supporting XeTeX out of the >> box this whole topic can (and should) be ignored. > So to summarize: > > - I should include the microtype package > - People using XeTeX need to tweak their setup anyway and can be > expected to know about all issues related to it. Yes. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Hi Ulf, Ulf Stegemann writes: > However, I'd strongly oppose to the claim that compatibility to the > latex compiler (vs. pdftex) is an academic problem. I know about > several LaTeX based systems that have to use the latex compiler simply > because pdftex can't handle eps graphics and converting those images > isn't feasible. So, while in the current case there's no compatibility > issue, I think it's reasonable to support both compilers. Are there still any systems in the wild that don't use pdftex for latex/dvi mode? Don't be fooled by the name, when pdftex is called in latex mode, it behaves exactly like the old tex/etex compiler and generates the same dvi documents, supports dvips and so on. For example on my Ubuntu 9.10 system 'latex -version' says: kheym...@ara:~$ latex -version pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6) kpathsea version 3.5.6 Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea is copyright 2007 Karl Berry and Olaf Weber. There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX using libpoppler copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX using libpoppler source. Primary author of pdfTeX using libpoppler: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea written by Karl Berry, Olaf Weber, and others. Compiled with libpng 1.2.37; using libpng 1.2.37 Compiled with zlib 1.2.3.3; using zlib 1.2.3.3 Compiled with libpoppler version 0.12.0 Or did I misunderstand your remark? Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Carsten Dominik writes: > On Apr 6, 2010, at 8:48 PM, Thomas S. Dye wrote: >> From the microtype documentation: >> >>> The microtype package does not work with XETEX. > > Does that mean it will break running XETEX, or will i just be ignored? It only gives a (harmless) warning: Package microtype Warning: You don't seem to be using pdftex. (microtype)All micro-typographic features will be disabled. But chances are high that most "normal" LaTeX documents will not work with xelatex anyways due to encoding or font selection issues, so I think unless org-mode aims at explicitely supporting XeTeX out of the box this whole topic can (and should) be ignored. Btw. current microtype does not support current luatex as well AFAIK, but that can be ignored too. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
"Thomas S. Dye" writes: > From the microtype documentation: > >> The microtype package does not work with XETEX. That's true, but supporting xetex requires many other changes too, for example only utf-8 input encoding is supported, the inputenc, fontspec and font packages may not be used, special xetex packages should be loaded and so on. Supporting XeTeX requires additional work anyway. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Carsten Dominik writes:
> On Apr 6, 2010, at 6:03 PM, Karsten Heymann wrote:
>> Carsten Dominik writes:
>>> On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
>>>> Carsten Dominik writes:
>>>>> \usepackage[AUTO]{inputenc}
>>>>> \usepackage[T1]{fontenc}
>>>>> \usepackage{graphicx}
>>>>> \usepackage{longtable}
>>>>> \usepackage{float}
>>>>> \usepackage{wrapfig}
>>>>> \usepackage{soul}
>>>>> \usepackage{latexsym}
>>>>> \usepackage{amssymb}
>>>>> \usepackage{hyperref}
[...]
>>> What is is really changing due to these last two
>>> settings (microtype) and tolerance, could you explain in a bit more
>>> detail?
[...]
> Thanks a lot for all this, I will follow your advice.
>
> One final question: Will any of these packages spoil the fun for
> people who want to process through .dvi instead of directly to pdf?
Not as far as I know. hyperref and microtype will run with reduced
features, but apart from that, there should be no problem. Regarding
microtype, I do not know what happens when it is used with the old TeX
or eTeX compiler that was used to created dvi's before pdftex was used
for this too, but that should largely be an academic problem as pdftex
is now used anywhere.
Yours
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Hi Carsten,
Carsten Dominik writes:
> On Apr 6, 2010, at 2:30 PM, Karsten Heymann wrote:
>> Carsten Dominik writes:
>>> \usepackage[AUTO]{inputenc}
>>> \usepackage[T1]{fontenc}
>>> \usepackage{graphicx}
>>> \usepackage{longtable}
>>> \usepackage{float}
>>> \usepackage{wrapfig}
>>> \usepackage{soul}
>>> \usepackage{latexsym}
>>> \usepackage{amssymb}
>>> \usepackage{hyperref}
>
> Do you have any recommendations for the sequence in which these
> packages should be called? Or does that make no difference at all?
> Does any of these cause problems if they are called twice (say I
> add them, but users have them configured already?)
The only critical one is hyperref, which should always be loaded last
(see
http://tug.ctan.org/tex-archive/macros/latex/contrib/hyperref/doc/manual.html#x1-30002).
> What is is really changing due to these last two
> settings (microtype) and tolerance, could you explain in a bit more
> detail?
I will try to explain it in my own poor words. microtype activates
advanced functions of the pdftex compiler (nowadays the standard TeX
compiler used by all distributions) to perform various subtle output
modifications, like shifting letters a tiny bit into the right margin so
that the margin looks *visually* aligned. Also it stretches and pulls
letters for tiny amounts so words fit better into paragraphs without
standing into the margin.
This is also the area where \tolerance takes action. It's a low level
TeX directive that controls how much the whitespace between words may
differ in width when typesetting a justified paragraph (I'm not sure
what the correct translation of the German word "Blocksatz" is). It's a
number in the range between 0 and (plus the special 10.000 meaning
infinite for TeX ;-) ). The standard value 200 is way much too
perfectionist for normal day-to-day typesetting, especially when writing
in languages where typical words are much longer then in English, like
German for example. Normal Desktop Text processors always operate in
"10.000"-Mode, meaning there's an infinite amount of whitespace allowed
between words, with the result of possibly large holes between the words
to keep the right margin aligned. TeX on the other hand will deny to
typeset paragraphs when it cannot find a solution (for the full
paragraph!) inside it's tolerance limits and write words into the right
margin so the author can manually fix the situation (rephrase, fix
hyphenation, ...). Tolerance values up to 2000 still look much better
than anything from Word/OOo and reduce the need to manually correct
these problems (and to explain this stuff to new users).
> And: Can I expect fixltx2e to be present in all distributions?
Yes, it's part of the latex base packages and thus always available
(given any not really really ancient LaTeX installation, e.g. more than
a decade).
> Is \tolerance defined in microtype, or did you put these together just
> incidentally?
They are completely independent.
>> Karsten
>
> I really appreciate expert advice about this. Thank you.
I'm more than glad my rusty LaTeX knowledge is of any use, especially to
the awesome org-mode community (and it's even more awesome author). If
you want advice from some *real* experts, ask in the comp.text.tex or
the de.comp.text.tex newsgroup. That's a completely different level, I'm
just some kind of semi-power-user that had too much time on university.
Yours
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Hi Carsten,
a small note:
Carsten Dominik writes:
[...]
> If you have customized the variable org-export-latex-classes, you need
> to remove the following lines from each class definition:
>
> \usepackage[AUTO]{inputenc}
> \usepackage[T1]{fontenc}
> \usepackage{graphicx}
> \usepackage{longtable}
> \usepackage{float}
> \usepackage{wrapfig}
> \usepackage{soul}
> \usepackage{latexsym}
> \usepackage{amssymb}
> \usepackage{hyperref}
The following packages should also be safe to add, as they are part of
the standard latex distribution:
textcomp (better Text symbols, for example list bullets not made of math
chars, are used automatically if package is loaded)
fixltx2e (numerous small slightly backwards incompatible changes, see
http://ctan.org/tex-archive/help/Catalogue/entries/fixltx2e.html)
Also, I'd recommend \usepackage{microtype} and a gentle increase of the
\tolerance value (less perfectionist text justification) for a much
nicer out-of-the-box experience:
\usepackage{microtype}
\tolerance=1000
Yours
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Hi,
Carsten Dominik writes:
> On Apr 4, 2010, at 12:50 AM, Henri-Paul Indiogine wrote:
>> When I export to LaTeX the line \definecolor. comes before
>> \usepackage{color} then it throws an error during compilation. If I
>> move the \definecolor... _after_ \usepackage{color} it compiles.
>>
>> Is are a way to setup my LaTeX export so that this happens
>> automagically?
>
> No, I think you need to return to the old way of configuring
> everything in org-export-latex-classes.
Suggestion: Would it be hard to add a location marker for the place the
default packages are included? Something like
(setq org-export-latex-classes
'(("book"
"\\documentclass[11pt]{book}
(include-org-standard-packages-here)
\\definecolor{darkblue}{rgb}{0.0,0.0,0.3}
\\hypersetup{colorlinks,breaklinks,
If (include-org-standard-packages-here) is missing, the \usepackage
lines are appended to the template. This way one could use the standard
packages and at the same time use commands from the packages in the
preamble.
Yours
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] LaTeX package dependencies
Carsten,
Carsten Dominik writes:
> seems like you know what you are talking about.
A little bit, although sadly I had few chances to actually use LaTeX
since I left the University. So I enjoy this even more :-)
> So maybe you can help me with this.
>
> I would like to
>
> 1. Require these packages with \usepackage or similar, but not
>have an error thrown when they are not available
>
> 2. Provide, as you say, alternative versions with providecommand.
>How would I do this? What do you mean by simple-text-alternatives?
I put the answer to both questions into a minimal example:
\documentclass{minimal} % should work with any document class
\IfFileExists{mnsymbol.sty}{%
\usepackage{mnsymbol}
}{%
\PackageWarning{orgmode}{mnsymbol.sty not found, using fall-back-replacements}
}
\providecommand*{\mnstar}{*} % provide alternative in case command not available
\begin{document}
\mnstar
\end{document}
Some notes:
- IfFileExists finds the sty file anywhere in the tex load
path (you can verify this with "kpsewhich FILE" on the commandline).
These commands are explained in the LaTeX Class writing guide:
texdoc clsguide
- \providecommand* is the same as \providecommand, but saves a tiny bit
of memory as no arguments are allowed that contain multiple
paragraphs (not making the *-variant the default for \providecommand
and \newcommand is in my opinion clearly a design flaw of LaTeX).
Hope to help,
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] LaTeX package dependencies
Hi, David Maus writes: > Carsten Dominik wrote: >>I am working on better entity (special symbol) support for >>export, based on a list Ulf Stegemann has compiled. >>The list Ulf has sent me requires the following LaTeX >>packages to be available: > >>* t1enc >>* textcomp >>* marvosym >>* wasysym >>* MnSymbol > On Debian GNU/Linux "Testing" these packages are available: > > , > | t1enc texlive-latex-base: /usr/share/texmf-texlive/tex/latex/base/t1enc.sty > | textcomp texlive-latex-base: > /usr/share/texmf-texlive/tex/latex/base/textcomp.sty > | marvosym texlive-fonts-recommended: > /usr/share/texmf-texlive/tex/latex/marvosym/marvosym.sty > | wasysym texlive-fonts-recommended: > /usr/share/texmf-texlive/tex/latex/wasysym/wasysym.sty > | MnSymbol texlive-fonts-extra: > /usr/share/texmf-texlive/tex/latex/mnsymbol/MnSymbol.sty > ` A small note on this: anything that's in tex/latex/base can be trusted to be included in any LaTeX installation (newer than ~10 years, probably ;-) ). Regarding marvosym, wasysym, mnsymbol: I think they are quite popular, but I would recommend to ship simple-text-alternatives via \providecommand for all symbols used from these packages. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [org-beamer] \alert
Hi,
i just catched up reading the org list, and I think I can contribute to
this:
Carsten Dominik writes:
> Is there a LaTeX command that can figure out if it is running a beamer
> class?
> If yes, a possible solution would be to redefine \alert in LaTeX when
> not doing BEAMER.
The LaTeX Command \providecommand behaves exactly like \newcommand iff
the command does not already exist, so one (untested) solution would be
\providecommand{\alert}[1]{\emph{#1}}
I think this would be the cleanest way, but keep in mind that the
special <> beamer parameters are not supported by standard latex
command creation commands.
Yours
Karsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: ordered list start with number other than 1
Hi, Shawn Koons writes: > Although it /would/ be nice to have it auto-magically begin numbering > starting at a particular number . I am using Lamport's book "LaTeX: > User's Guide and Reference Manual" to see if there may be a LaTeX > answer to this problem. http://en.wikibooks.org/wiki/LaTeX/Formatting#Customizing_Enumerated_Lists Also the LaTeX Companion, 2nd ed. should contain something about it, but I don't have it here at wort so I can't look up. Yours Karsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] iCal export - possible timezone bug
Hi, Richard Riley writes: > Where is the best place to set this TZ in a Linux environment so that > emacs picks it up on a gnome desktop? > > I tried in my .xinitrc and my .bashrc and my /etc/bash.bashrc and it > didn't seem to pick up for the export correctly. .xinitrc or .xsession would be my choice too. Of cource you have to make sure that those files are actually used, usually you have to choose "custom session" or similiar in the gdm login screen. Yours Karsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Customizing HTML Export
Hello Peter,
Peter Jones <[EMAIL PROTECTED]> writes:
> I realize that LaTex is a better way to go to PDF, but I do have some
> concerns:
> 2. The default fonts used when converting LaTex to PDF are ugly, to
> say the least
Just a note: If you put \usepackage{lmodern} before the
\begin{document} line of every LaTeX document you write, you'll never
have to worry about ugly fonts in PDF again (there are many other
solutions to this problem, but this is the easiest).
Yours
Karsten
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode and taskpaper
"Egli Christian (KIRO 433)" <[EMAIL PROTECTED]> writes: >> the recent discussion about Taskpaper in the thread started by >> Clint Laskowski has made me realize how much we have lost out way >> with Org-mode. Org-mode was once a compact and easy tool just like >> taskpaper. In fact, looking at the features of taskpaper, one >> might think that they had an older version of Org-mode as model and >> goal of their development. > > Hm, reading all the answers to this aprils fools gets me a bit > worried. Nobody seems to see the joke and everybody seems to agree > that org-mode is too bloated. Now you spoiled it :-) Yours, Karsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
