Re: [O] Bug: org-read-date: problem with year in dotted european date input [7.9.2 (release_7.9.2-436-g9b11e6 @ /home/grfz/src/org-mode/lisp/)]
I fixed the documentation. - Carsten On 14.10.2012, at 09:57, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> Org used to have the ambition to parse a date in the middle of a text, >> and this six what you are seeing in the documentation. However, over >> time more and more different requests came in, to parse ISO weeks, >> European dates and more. Also we want to allow incomplete dates like >> leaving out a year etc. I still think Org does a pretty god job >> there. However, to be reasonably predictable we did have o restrict >> matching of special dates to the beginning of the string, and this is >> what you and Nicolas are now seeing. > > It may be worth specifying that restriction in the documentation. As > Gregor pointed out > >But it will in fact accept any string containing some date > and/or time information, and it is really smart about interpreting your > input. > > is misleading. > > > Regards, > > -- > Nicolas Goaziou
Re: [O] New LaTeX exporter and superscripts
Aloha Nicolas,
Yes, it exports correctly now.
Thanks for your good work.
All the best,
Tom
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The following input:
>>
>> Fifteen ^{14}C age determinations from 11 inland temples were reported
>> by [[textcite:mccoy11:_strat_hawaii][Table 2;;ref]]. A single ^{14}C age
>> determination on a piece of short-lived
>>
>> exports to LaTeX like this:
>> Fifteen $^\mathrm{14}$C age determinations from 11 inland temples
>> were reported by
>> \textcite[][Table 2]{mccoy11:_strat_hawaii}. A single \^\{14\}C age
>> determination on a piece of short-lived
>>
>> Note the different translations of ^{14}C.
>
> This should be fixed now. Thanks for reporting it.
>
>
> Regards,
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] nbsp and /italics/
Thanks Nicolas,
Works like magic.
All the best,
Tom
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Using the filter you kindly provided (below) and this construct, "/Sida/
>> cf. /fallax/" I get the following incorrect LaTeX export, "\emph{Sida}
>> cf.~/fallax/". I'm expecting "\emph{Sida} cf.~\emph{fallax}".
>
> This is because `org-emph-re' only accepts the beginning of line,
> a white space, a tab, or any symbol among ('\"{ before emphasis markup.
> Hence, _ (nobreak space) prevents identification of italics.
>
> You may add _ to "pre" part of `org-emphasis-regexp-components'.
>
>
> Regards,
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] Org-sync with redmine
On Sun, Oct 14, 2012 at 3:05 AM, Tim wrote: > Any idea where i should look for what may be causing the error ? The redmine backend is incomplete and poorly tested, sorry. Unfortunately, I'm very busy and I have not found the time to work on org-sync yet. The redmine backend is at the top of my TODO list though.
Re: [O] Trouble with in-line images and iimage.el
On Sat, Oct 13, 2012 at 2:31 PM, Joao Brito wrote: > John Hendy gmail.com> writes: > >> I had to track down a bunch of .dlls and copy them into my Emacs bin/ >> directory. From there it worked. For the record, I added the following > > Thanks, John, it worked for me too. It was easier than I thought, I've never > noticed I didn't have these libraries. Yay -- glad it helped! It was frustrating hunting around and not getting this to work. Such a neat feature. John > > > >
Re: [O] nbsp and /italics/
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Using the filter you kindly provided (below) and this construct, "/Sida/
> cf. /fallax/" I get the following incorrect LaTeX export, "\emph{Sida}
> cf.~/fallax/". I'm expecting "\emph{Sida} cf.~\emph{fallax}".
This is because `org-emph-re' only accepts the beginning of line,
a white space, a tab, or any symbol among ('\"{ before emphasis markup.
Hence, _ (nobreak space) prevents identification of italics.
You may add _ to "pre" part of `org-emphasis-regexp-components'.
Regards,
--
Nicolas Goaziou
Re: [O] New LaTeX exporter and superscripts
Hello,
Rasmus writes:
> Another (bug?) is that
>
> 1. $x$
> 2. $y$
>
> exports as
>
> \begin{enumerate}
> \item \$x\$
> \item \$y\$
> \end{enumerate}
> (also true for itemize).
This one should also be fixed. Thank you.
> Also, [org] $x$'s is exported as [LaTeX] $x$`s, which is also wrong.
Yes, smart quotes are defective in new exporter. I already have a bug
report (from you) about it. I suggest disabling, i.e.
`org-e-latex-quotes' for now.
Regards,
--
Nicolas Goaziou
Re: [O] New LaTeX exporter and superscripts
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> The following input:
>
> Fifteen ^{14}C age determinations from 11 inland temples were reported
> by [[textcite:mccoy11:_strat_hawaii][Table 2;;ref]]. A single ^{14}C age
> determination on a piece of short-lived
>
> exports to LaTeX like this:
> Fifteen $^\mathrm{14}$C age determinations from 11 inland temples were
> reported by
> \textcite[][Table 2]{mccoy11:_strat_hawaii}. A single \^\{14\}C age
> determination on a piece of short-lived
>
> Note the different translations of ^{14}C.
This should be fixed now. Thanks for reporting it.
Regards,
--
Nicolas Goaziou
Re: [O] New LaTeX exporter and superscripts
t...@tsdye.com (Thomas S. Dye) writes:
> Fifteen ^{14}C age determinations from 11 inland temples were reported
> by [[textcite:mccoy11:_strat_hawaii][Table 2;;ref]]. A single ^{14}C
> age
> determination on a piece of short-lived
>
> exports to LaTeX like this:
> Fifteen $^\mathrm{14}$C age determinations from 11 inland temples were
> reported by
> \textcite[][Table 2]{mccoy11:_strat_hawaii}. A single \^\{14\}C age
> determination on a piece of short-lived
>
> Note the different translations of ^{14}C.
I have observed this as well.
Another (bug?) is that
1. $x$
2. $y$
exports as
\begin{enumerate}
\item \$x\$
\item \$y\$
\end{enumerate}
(also true for itemize).
Also, [org] $x$'s is exported as [LaTeX] $x$`s, which is also wrong.
Cheers,
Rasmus
--
. . . It begins of course with The Internet. A Net of Peers.
[O] org-pretty-entities and symbols like M_x^y
Hi I was wondering if there is a way to fontify expressions like M_x^y correctly with org-pretty-entities. M_x^y displays the subscript x correctly but not the superscript y. M^y_x displays the superscript y correctly but not the subscript x. Regards, Laurent
[O] New LaTeX exporter and superscripts
Aloha Nicolas,
The following input:
Fifteen ^{14}C age determinations from 11 inland temples were reported
by [[textcite:mccoy11:_strat_hawaii][Table 2;;ref]]. A single ^{14}C age
determination on a piece of short-lived
exports to LaTeX like this:
Fifteen $^\mathrm{14}$C age determinations from 11 inland temples were reported
by
\textcite[][Table 2]{mccoy11:_strat_hawaii}. A single \^\{14\}C age
determination on a piece of short-lived
Note the different translations of ^{14}C.
I think this popped up recently, but I wasn't paying close attention, so
can't say with any certainty.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] nbsp and /italics/
Arghh. I should have pointed out that this is the new exporter, and
that the first argument to replace-regexp-in-string is an alternative
underscore, not the blank space that shows up in my gnus.
Tom
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha Nicolas,
>
> Using the filter you kindly provided (below) and this construct, "/Sida/
> cf. /fallax/" I get the following incorrect LaTeX export, "\emph{Sida}
> cf.~/fallax/". I'm expecting "\emph{Sida} cf.~\emph{fallax}".
>
> All the best,
> Tom
>
> #+name: ngz-nbsp
> #+begin_src emacs-lisp
> (defun ngz-latex-filter-nobreaks (text backend info)
> "Ensure \"_\" are properly handled in Beamer/LaTeX export."
> (when (memq backend '(e-beamer e-latex))
> (replace-regexp-in-string " " "~" text)))
> (add-to-list 'org-export-filter-plain-text-functions
> 'ngz-latex-filter-nobreaks)
> #+end_src
--
Thomas S. Dye
http://www.tsdye.com
[O] nbsp and /italics/
Aloha Nicolas,
Using the filter you kindly provided (below) and this construct, "/Sida/
cf. /fallax/" I get the following incorrect LaTeX export, "\emph{Sida}
cf.~/fallax/". I'm expecting "\emph{Sida} cf.~\emph{fallax}".
All the best,
Tom
#+name: ngz-nbsp
#+begin_src emacs-lisp
(defun ngz-latex-filter-nobreaks (text backend info)
"Ensure \"_\" are properly handled in Beamer/LaTeX export."
(when (memq backend '(e-beamer e-latex))
(replace-regexp-in-string " " "~" text)))
(add-to-list 'org-export-filter-plain-text-functions
'ngz-latex-filter-nobreaks)
#+end_src
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] Bib file path relative to home using tilde ~ in Ubuntu
Vladimir Lomov writes: > Hello, > ** Sanjib Sikder [2012-10-14 11:53:52 +0530]: > >> Hi, >> > >>> First of all can you confirm your .bashrc setting is working.? > >>> in the terminal >>> --8<---cut here---start->8--- >>> echo $BIBINPUTS > >> --8<---cut here---end--->8--- > > >> *Here is the output* > >> ~$ echo $BIBINPUTS >> .//:/home/USERNAME/bst//:.//:/home/USERNAME/bibFiles//: >> -- > >>> and also can you check what is the value of BIBINPUTS in emacs.? Within >>> Emacs >>> evaluate the following (either in scratch buffer or with key press `M-:' or >>> with `M-x eval-expression') > >>> --8<---cut here---start->8--- >>> (getenv "BIBINPUTS") >>> --8<---cut here---end--->8--- > > > >> *OUTPUT* is: nil >> - > >>> May be the last resort would be setting the variable within your .emacs > >>> --8<---cut here---start->8--- >>> (setenv "BIBINPUTS" ".:$HOME/bib:") >>> --8<---cut here---end--->8--- > > >> I will try this one >> - > >> BTW how you are starting emacs? (command line or gui mouse click?) > > >> I am starting emacs from GUI mouse click. All the above tests are done only >> with the .bashrc, i.e., after removing the lines from .profile and .gnomerc > > You use incorrert path for bibtex files, use > $HOME/texmf/bibtex/bib > this is the standard. I don't know which TeX distribution Ubuntu uses. If it is one of the distributions with kpathsea, then "kpsepath bib" should list standard paths that will be searched for bibtex files. My system shows nine locations, including three under my home directory. These locations work regardless of how emacs is started (from a shell or the gui). hth, Tom > > latex as well as bibtex searches for files in standard paths, like the one > above. If your files located in other places you have to set env. > variables (TEXINPUTS and BIBINPUTS). However setting env. variables is a > bit tricky. If one uses only terminal session it is enough to set > variables in apropriate RC files: bash uses ~/.bash_profile and > ~/.bashrc depending on type of shell (login or not), for zsh see manual. > When run graphical session it depends what DE and DM are used. GNOME, > Unity launched by gdm or lightdm read user settings from ~/.profile > > --- > WBR, Vladimir Lomov -- Thomas S. Dye http://www.tsdye.com
Re: [O] Headings in agenda view
Le dimanche 14 oct 2012 à 09:00:05 (+), Renger van Nieuwkoop a écrit :
> Hi
>
> I have the following agenda-view in Org-Mode
> ("p" "Week plan"
> ((tags-todo "Monday")
> (tags-todo "Tuesday")
> (tags-todo "Wednesday")
> (tags-todo "Thursday")
> (tags-todo "Friday")
> (tags-todo "Saturday")
> (tags-todo "Sunday"))
>nil)
>
> And would like to have a heading for every day. I tried using
>(org-agenda-overriding-header "Monday"),
> (org-agenda-overriding-header "Tuesday"), etc.
> at several positions, but I did not manage, to get the headers.
> Any hint would be more than welcome.
> Cheers
> Renger
Hi Renger,
The following works for me:
("p" "Week plan"
((tags-todo "Monday" ((org-agenda-overriding-header "Monday")))
(tags-todo "Tuesday" ((org-agenda-overriding-header "Tuesday")))
(tags-todo "Wednesday" ((org-agenda-overriding-header "Wednesday")))
(tags-todo "Thursday" ((org-agenda-overriding-header "Thursday")))
(tags-todo "Friday" ((org-agenda-overriding-header "Friday")))
(tags-todo "Saturday" ((org-agenda-overriding-header "Saturday")))
(tags-todo "Sunday" ((org-agenda-overriding-header "Sunday"
((org-agenda-compact-blocks t)) nil)
PS: I have added compact block, just because I find it looks nicer; feel
free to remove it!
Best,
François.
--
http://francois.allisson.co
Re: [O] Bib file path relative to home using tilde ~ in Ubuntu
Hello Nicholas, Very good explanation. Its like reading a standard textbook. Thank you very much for your continuous help to org community. Nick Dokos writes: > Sanjib Sikder wrote: > >> Hi, >> >> "The easiest way to update is logout from the computer, login again and >> start emacs." >> >> I did that. Still not working :( >> > > When you have problems like this, you need to take it in small > steps. > > o What shell are you using? Yagnesh's recommendation assumes > that you are running bash as your shell (presumably on some > Linux/Unix system). Is this assumption correct? > > o Assuming you are using bash, there are two relevant initialization > files: a login shell sources $HOME/.profile and any shell (be it a login > shell or one that is started as a descendant of your login shell) sources > $HOME/.bashrc. > > o Adding > > export FOO=bar > > to such an initialization file causes the variable FOO to be defined (with > value "bar") > and to be exported (i.e. it is available in the environment of *any* > subprocess of > this shell). > > o So log out and log back in[fn:2], start a shell and at the prompt say > > echo $FOO > > Does it say "bar"? If not, don't go any further: the problem has nothing to > do with > emacs (note that this is the first time I mention emacs). > > o If this part is OK, start emacs *from this shell*: it should inherit the > variable. > You can check by evaluating this form: > > (getenv "FOO") > > Then the variable will also be available to any subprocesses started by > emacs. > > o In particular, if you define BIBINPUTS as Yagnesh suggests, then the bibtex > invoked > by the latex exporter under emacs will find the bib file where you told it. > > o What can go wrong? The usual problem is that you use some graphical > desktop environment and start emacs by clicking on some icon. Then > the emacs process does not have a bash shell as its parent, so it does > not inherit the exported variables. Try starting emacs from a bash > command line.[fn:2] > > Nick > > Footnotes: > [fn:1] If you define it in .bashrc, you shouldn't have to log out and log >back in: just start a new bash shell. > > [fn:2] I prefer defining variables in my .profile and I have arranged >for my .profile to be sourced by the appropriate initialization >file of my graphical desktop environment, so I get it whether I >log in at the console or through the graphical login. That >way *every* process, no matter how it is started, has the >variables available to it. I use .bashrc only for aliases (which >I use very rarely, so most of the time I don't have a .bashrc >file at all). > > > Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు YYR
Re: [O] org 7.9.2 - Search - Args out of range [SOLVED]
Sorry for the false alarm. Some messup in my org mode installation.
Definitely not a problem of 7.9.2.
Martin
Am 14.10.2012 11:05, schrieb G. Martin Butz:
Hi,
I recently upgraded to org 7.9.2. A simple search (e.g. for "Jullien")
now brings the following error (which does not seem to be related to the
search itself, but some font face problem)
--8<---
org-get-todo-face: Args out of range: #(" jullien:" 0 14
(org-category "jullien" tags nil org-highest-priority 65
org-lowest-priority 67 time-of-day nil ...)), 14, 18
--8<---
Does anyone know, what I can do about it?
Cheers
Martin
[O] org 7.9.2 - Search - Args out of range
Hi,
I recently upgraded to org 7.9.2. A simple search (e.g. for "Jullien")
now brings the following error (which does not seem to be related to the
search itself, but some font face problem)
--8<---
org-get-todo-face: Args out of range: #(" jullien:" 0 14
(org-category "jullien" tags nil org-highest-priority 65
org-lowest-priority 67 time-of-day nil ...)), 14, 18
--8<---
Does anyone know, what I can do about it?
Cheers
Martin
--
| G. Martin Butz, m...@mkblog.org, 0421 98749324, www.mkblog.org |
[O] Headings in agenda view
Hi
I have the following agenda-view in Org-Mode
("p" "Week plan"
((tags-todo "Monday")
(tags-todo "Tuesday")
(tags-todo "Wednesday")
(tags-todo "Thursday")
(tags-todo "Friday")
(tags-todo "Saturday")
(tags-todo "Sunday"))
nil)
And would like to have a heading for every day. I tried using
(org-agenda-overriding-header "Monday"),
(org-agenda-overriding-header "Tuesday"), etc.
at several positions, but I did not manage, to get the headers.
Any hint would be more than welcome.
Cheers
Renger
Modelworks
Gewerbestrasse 15
3600 Thun - Switzerland
+41 79 818 53 73
i...@modelworks.ch
blog.modelworks.ch
Re: [O] possible bug? org-indent-mode breaks org-clock-display
Hello, Not Sure writes: > I am using > > Org-mode version 7.9.2 (7.9.2-44-g93f4b7-elpa @ > /home/johannes/.emacs.d/elpa/org-20121008/) > > and have the following problem: > > After I clocked some work I have done and issue the command > org-clock-display, the subtotals are only displayed if the buffer is not > currently in org-indent-mode. Switching modes will solve the problem. If > I switch back the problem comes back. > > I attached two screenshots of the two states. I see the subtotal in both pictures. Is it intended? Regards, -- Nicolas Goaziou
Re: [O] Bug: org-read-date: problem with year in dotted european date input [7.9.2 (release_7.9.2-436-g9b11e6 @ /home/grfz/src/org-mode/lisp/)]
Hello, Carsten Dominik writes: > Org used to have the ambition to parse a date in the middle of a text, > and this six what you are seeing in the documentation. However, over > time more and more different requests came in, to parse ISO weeks, > European dates and more. Also we want to allow incomplete dates like > leaving out a year etc. I still think Org does a pretty god job > there. However, to be reasonably predictable we did have o restrict > matching of special dates to the beginning of the string, and this is > what you and Nicolas are now seeing. It may be worth specifying that restriction in the documentation. As Gregor pointed out But it will in fact accept any string containing some date and/or time information, and it is really smart about interpreting your input. is misleading. Regards, -- Nicolas Goaziou
Re: [O] Bib file path relative to home using tilde ~ in Ubuntu
Hello, ** Sanjib Sikder [2012-10-14 11:53:52 +0530]: > Hi, > >> First of all can you confirm your .bashrc setting is working.? >> in the terminal >> --8<---cut here---start->8--- >> echo $BIBINPUTS > --8<---cut here---end--->8--- > *Here is the output* > ~$ echo $BIBINPUTS > .//:/home/USERNAME/bst//:.//:/home/USERNAME/bibFiles//: > -- >> and also can you check what is the value of BIBINPUTS in emacs.? Within >> Emacs >> evaluate the following (either in scratch buffer or with key press `M-:' or >> with `M-x eval-expression') >> --8<---cut here---start->8--- >> (getenv "BIBINPUTS") >> --8<---cut here---end--->8--- > *OUTPUT* is: nil > - >> May be the last resort would be setting the variable within your .emacs >> --8<---cut here---start->8--- >> (setenv "BIBINPUTS" ".:$HOME/bib:") >> --8<---cut here---end--->8--- > I will try this one > - > BTW how you are starting emacs? (command line or gui mouse click?) > I am starting emacs from GUI mouse click. All the above tests are done only > with the .bashrc, i.e., after removing the lines from .profile and .gnomerc You use incorrert path for bibtex files, use $HOME/texmf/bibtex/bib this is the standard. latex as well as bibtex searches for files in standard paths, like the one above. If your files located in other places you have to set env. variables (TEXINPUTS and BIBINPUTS). However setting env. variables is a bit tricky. If one uses only terminal session it is enough to set variables in apropriate RC files: bash uses ~/.bash_profile and ~/.bashrc depending on type of shell (login or not), for zsh see manual. When run graphical session it depends what DE and DM are used. GNOME, Unity launched by gdm or lightdm read user settings from ~/.profile --- WBR, Vladimir Lomov -- Walk softly and carry a big stick. -- Theodore Roosevelt
