Re: [O] [ISSUE] links navigation not consistent behavior
Nicolas Goaziou writes: > Hello, > > stardiviner writes: >> #+begin_src org >> https://www.bing.com >> >> ,* link in properties drawer >> :PROPERTIES: >> :URL: http://www.google.com >> :END: >> >> https://www.bing.com >> >> ,* http(s) url in content of headline >> >> https://www.baidu.com >> #+end_src > >> In upper example, when I link jumping from first link to next, it will skip >> the >> url in properties drawer. > > This is expected. > > The value in a properties drawer cannot be a link, even though > `org-open-at-point' would normally open it, as is done for comments. I see. > > In addition to no being syntactically a valid link, I think it is > undesirable for an interactive command to display hidden internal data. > > If you want to reach it, just write a function calling > >(re-search-forward org-any-link-re nil t) Thanks for this advice. > >> When I try to jump backwards, some times reports "no further link found", >> like >> when I'm on the last link. > > I think I fixed this. Thanks again for your work. :) > > Thank you. > > Regards, Have a nice day, Nicolas. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: [O] How to avoid \title{} and \date{} in latex export
Thank you very much for all answer and advices!
Best regards,
Flávio
On Thu, Apr 11, 2019 at 4:32 PM Jeremie Juste
wrote:
>
> Hello Flavio,
>
> I believe you meant
>
> #+OPTIONS:date:nil title:nil
>
> Notice the "s" at the end of option
>
> Hope this helps,
>
> Jeremie
>
> Flavio Leonardo Cavalcanti de Moura writes:
>
> > Hello,
> >
> > My org file uses a latex class that, after exporting, is in conflict with
> > the lines \date{} and \title{} automatically generated by orgmode latex
> > export. I already tried the following headings for the org file:
> >
> > 1.
> > #+TITLE:
> > #+DATE:
> >
> > 2.
> > #+TITLE:
> >
> > #+option: date:nil
> >
> > 3.
> >
> > #+option: title:nil date:nil
> >
> > But in all cases the lines
> > \title{}
> > \date{}
> > are in the tex file automatically generated by the export engine. Is
> there
> > a way to prevent the addition of these lines?
> >
> > Best regards,
> > Flávio.
>
Re: [O] orgalist-mode: wrong indentation in message mode after recent change in emacs
> The third is why indent-according-to-mode hard-codes the check for > indent-relative and indent-relative-first-indent-point. Wouldn't it be > nice if this check instead looked up some variable akin to > electric-indent-functions-without-reindent, that can be more easily > customised? Agreed. Comparing functions is always fraught with dangers, as we are witnessing here (this very fundamental problem was arguably the original motivation for inventing type-classes in Haskell to avoid the ugly ad-hoc "eqtypes" of SML). We need the comparison here for backward compatibility, but we should supplement it with a variable, like we did with `electric-indent-inhibit` (and not with electric-indent-functions-without-reindent which just suffers from the same fundamental problem). Stefan
Re: [O] How to avoid \title{} and \date{} in latex export
Hello Flavio,
I believe you meant
#+OPTIONS:date:nil title:nil
Notice the "s" at the end of option
Hope this helps,
Jeremie
Flavio Leonardo Cavalcanti de Moura writes:
> Hello,
>
> My org file uses a latex class that, after exporting, is in conflict with
> the lines \date{} and \title{} automatically generated by orgmode latex
> export. I already tried the following headings for the org file:
>
> 1.
> #+TITLE:
> #+DATE:
>
> 2.
> #+TITLE:
>
> #+option: date:nil
>
> 3.
>
> #+option: title:nil date:nil
>
> But in all cases the lines
> \title{}
> \date{}
> are in the tex file automatically generated by the export engine. Is there
> a way to prevent the addition of these lines?
>
> Best regards,
> Flávio.
[O] How to avoid \title{} and \date{} in latex export
Hello,
My org file uses a latex class that, after exporting, is in conflict with
the lines \date{} and \title{} automatically generated by orgmode latex
export. I already tried the following headings for the org file:
1.
#+TITLE:
#+DATE:
2.
#+TITLE:
#+option: date:nil
3.
#+option: title:nil date:nil
But in all cases the lines
\title{}
\date{}
are in the tex file automatically generated by the export engine. Is there
a way to prevent the addition of these lines?
Best regards,
Flávio.
Re: [O] Handling bilingual text in single org file?
> Am 11.04.2019 um 16:28 schrieb Loris Bennett :
>
> Hi,
>
> I have a text I would like to keep in a single org file in both an
> English and a German version.
>
> I could just have first one version and the other and export via tags.
> However, ideally I would like to keep both versions of a given paragraph
> close together to allow easier translation and editing. It would
> potential be nice to be able to fold up one language to just view the
> other.
>
> Does anyone have a good workflow for this use-case?
I had the same question about a year ago.
Here is what I came up with.
It works on section (subsection) level, not on paragraph level.
I can either export one language or both for comparison.
I’ve used yasnippets to insert the @@latex environments.
You can select which language to export by removing the space in the
+SELECT_TAGS: line.
#+OPTIONS: ':t *:t -:t ::t <:t H:3 \n:nil ^:{} arch:headline author:t
#+OPTIONS: broken-links:nil c:nil creator:nil d:(not "LOGBOOK")
#+OPTIONS: date:t e:t email:nil f:t inline:t num:t p:nil pri:nil
#+OPTIONS: prop:nil stat:t tags:nil tasks:t tex:t timestamp:t title:t
#+OPTIONS: toc:nil todo:t |:t
#+TITLE: Übersetzung
#+DATE: <2017-12-08 Fri>
#+AUTHOR: Axel Kielhorn
#+LANGUAGE: de
# +SELECT_TAGS: export german
# +SELECT_TAGS: export english
#+EXCLUDE_TAGS: noexport new glossar
#+CREATOR: Emacs 25.3.1 (Org mode 9.1.2)
#+LATEX_CLASS: komaarticle
#+LATEX_CLASS_OPTIONS: [english, german]
# +LATEX_HEADER: \usepackage[noindent,parskip]{stdpage}
#+TAGS_ALL: german english new glossar
* Text deutsch:german:
@@latex:\begin{otherlanguage}{german}@@
Hier ist ein Text.
@@latex:\end{otherlanguage}@@
* Text englisch :english:
@@latex:\begin{otherlanguage}{english}@@
Here is some text.
@@latex:\end{otherlanguage}@@
This was used for one smallish project.
Most of my documents are german only.
Greeting Axel
[O] Handling bilingual text in single org file?
Hi, I have a text I would like to keep in a single org file in both an English and a German version. I could just have first one version and the other and export via tags. However, ideally I would like to keep both versions of a given paragraph close together to allow easier translation and editing. It would potential be nice to be able to fold up one language to just view the other. Does anyone have a good workflow for this use-case? Cheers, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
Re: [O] How to avoid \title{} and \date{} in latex export
Hi,
+1 for not supporting Elsevier.
Nonetheless, if you *have* to use this template, or if you encounter
similar issues with another one, I've used the following workaround in
the past:
- export just the body of the article (hitting C-b at the export frame)
- input that at your tex file using \input{}
Cheers,
Georgios
On 11/04/2019 06:01, Nick Dokos wrote:
> Flavio Leonardo Cavalcanti de Moura writes:
>
>> Hi Jilius,
>>
>> Thank you very much for your reply. It is a good idea, but the latex
>> class I am using (entcs) has its own \title and \date, and by
>> renewing the command I overwrite both...
>>
>> I am removing these lines by hand from the tex file generated by the
>> export engine... but it is not nice. Any help is very much
>> appreciated!
>
> If I were you, I would write it all using the article class, then once
> satisfied, I would export it to a latex file, make the necessay
> changes (article -> entcs, frontmatter included) and then process it
> through latex one final time. It is just not worth fighting against
> the peculiarities of the entcs class or trying to bring it into
> submission: it's just a badly written class.
>
> But I would also suggest that you consider publishing your paper in a
> different journal. Elsevier is a toxic publisher and is being
> boycotted by many prominent scientists. See
>
> http://thecostofknowledge.com/
>
> and Timothy Gowers' blog:
>
> https://gowers.wordpress.com/category/elsevier/
>
>>
>> Best regards,
>> Flávio.
>>
>>
>> Hi Flávio,
>>
>> perhaps you could add something like (untested)
>>
>> #+LATEX_HEADER: \renewcommand{\title}[1]{} \renewcommand{\date}[1]{}
>>
>> to your org-file? It's not exactly what you asked for, but it might
>>
>> alleviate your problem.
>>
>> HTH,
>>
>> Julius
>>
>> Am 10.04.19 um 18:10 schrieb Flavio Leonardo Cavalcanti de Moura:
>>
>> > Hello,
>>
>> >
>>
>> > My org file uses a latex class that, after exporting, is in
>> conflict with
>>
>> > the lines \date{} and \title{} automatically generated by orgmode
>> latex
>>
>> > export. I already tried the following headings for the org file:
>>
>> >
>>
>> > 1.
>>
>> > #+TITLE:
>>
>> > #+DATE:
>>
>> >
>>
>> > 2.
>>
>> > #+TITLE:
>>
>> > #+option: date:nil
>>
>> >
>>
>> > 3.
>>
>> > #+option: title:nil date:nil
>>
>> >
>>
>> > But in all cases the lines
>>
>> > \title{}
>>
>> > \date{}
>>
>> > are in the tex file automatically generated by the export engine.
>> Is there
>>
>> > a way to prevent the addition of these lines?
>>
>> >
>>
>> > Best regards,
>>
>> > Flávio.
>>
>> >
>>
>
--
--
Georgios Kaklamanos
Doctoral Student, e-Science Group, GWDG
mailto: georgios.kaklama...@gwdg.de
Telefon: 0551 201-26803
--
GWDG - Gesellschaft für wissenschaftliche
Datenverarbeitung mbH Göttingen
Am Faßberg 11, 37077 Göttingen, Germany
WWW: www.gwdg.demailto: g...@gwdg.de
Phone: +49 (0) 551 201-1510
Fax: +49 (0) 551 201-2150
--
Geschäftsführer: Prof. Dr. Ramin Yahyapour
Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger
Sitz der Gesellschaft: Göttingen
Registergericht: Göttingen
Handelsregister-Nr. B 598
--
Zertifiziert nach ISO 9001
--
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [O] Regresssion in org-capture?
Hello,
With the last version from org ELPA, I can confirm that the bug is fixed.
Thanks,
Roland.
Nicolas Goaziou writes:
> Hello,
>
> Roland Everaert writes:
>
>> Since a few weeks, the following template didn't work anymore.
>>
>> (setq org-capture-templates
>> `(("b" "Add url to bookmarks DB" entry (file+headline
>> "~/org/private/bookmarks.org" "URLs")
>> "** %i\n" :immediate-finish t))
>> )
>>
>> Anytime I execute it I got this error:
>>
>> org-capture: Capture template ‘b’: Template is not a valid Org entry
>> or tree
>
> Fixed. Thank you.
>
> Regards,
--
Luke, use the FOSS
Sent from Emacs
