Re: `:export' attribute?: Re: Experimental public branch for inline special blocks

Juan Manuel Macías writes: >>> :export "latex+ html+ rest*" >> "rest" might be a valid backend name. > I will try to implement the "rest" option. What about "others" or even ":others" as a placeholder for any not explicitly mentioned export backend? Another quick thought crossing my mind:

Re: Experimental public branch for inline special blocks

Hi Juan, first of all: Thank you for your great work. Looks really good. Just out of curiosity: Why a special syntax for alias expansion? >From a syntax and user point of view, I think I would prefer a simpler syntax. So {text} would check if an alias is registered and if yes use it. This

Re: New Orgmode LaTex Document Class ?

Ihor Radchenko writes: > I'd prefer to put some more generic reference. Some info manual or > good stable URL link that has explanations about kpsewhich and other > LaTeX basics. What about http://mirrors.ctan.org/info/latex-doc-ptr/latex-doc-ptr.pdf No direct references to kpsewhich, but

Re: New Orgmode LaTex Document Class ?

David Masterson writes: > I want to install a resume document class for LaTex There are the variables org-latex-classes and org-latex-default-class on the Org side, but that's only about some structural metadata (how to map Org headline levels to LaTeX structure macros). To find the new class

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > Though ideally all the necessary fonts should be provided by > TeXLive. I am not sure why they are not yet there in 2023. First problem: Is there any free/libre font out there that has a really broad and comprehensive coverage of Unicode glyphs? I really don't know, but

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > AFAIR, the basic problem is that we cannot guarantee that any given > UTF font is installed. Yes, indeed. Probably the best route is to make tweaking as easy as possible. There are still too few (if any) really comprehensive (and good looking) Unicode fonts available.

Re: exporting to PDF multi-lingual document

"Dr. Arne Babenhauserheide" writes: > Isn’t the speed more relevant for large documents? I always had the impression that luatex has mostly a rather fixed overhead. Maybe that's because many of my larger documents make quite some use of TikZ and most time may be spend there. Therefore I assumed

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > The downside of lualatex is that it is slower: > https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/ BTW: One of the discussion points in that thread has been the problem of default fonts. With pdflatex the default font is CM (Computer Modern) and if the

Re: exporting to PDF multi-lingual document

Ihor Radchenko writes: > The downside of lualatex is that it is slower: > https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/ Yes, for sure. But I have the impression that newer versions of luatex have become a bit faster (maybe it's just a subjective impression that I want to be true,

Re: exporting to PDF multi-lingual document

andrés ramírez writes: > I have tried the snippet. But It shows just Japanese and the other > paragraphs are not present on the PDF. That's quite strange. I just re-tested with emacs -Q (Emacs 28.2 with integrated Org 9.5.5). It generates the following tex file: --8<---cut

Re: exporting to PDF multi-lingual document

Hi. I got curious and it seems if you are willing to use lualatex (which is, I think, currently the most actively developed engine and nowadays a really good choice), the following solution should work: --8<---cut here---start->8--- #+TITLE: Doc multi-lingual

Re: [RFC] Refactoring org-element API

Hi Ihor, thank you for all your great work. I did not dive deep into all the details, but the overview you provided sounds sensible. One minor nitpick: I would prefer a function like ~org-element-property-1~ to be named e.g. ~org-element-property-lazy~ (or something similar), because the "-1" is

Re: [POLL] Proposed syntax for timestamps with time zone info

Jean Louis writes: > Specifying time zone is not ambiguous as long as you use the TZ > database for specifications! That's wrong and you know it. For example [2023-10-29 02:30 @Europe/Berlin] is ambiguous. Period. And that some examples got a bit off has been quite obvious and has already

Re: [POLL] Proposed syntax for timestamps with time zone info

Ihor Radchenko writes: > Note that an alternative is > [2022-11-12 10:30-11:00] > [2022-11-12 10:30-11] > [2022-11-12 10:30-11:00-11] > which is much less confusing. Hmmm... is it? I read a lot different timestamps these days and currently I'm very careful reading them, especially while

Re: [POLL] Proposed syntax for timestamps with time zone info

writes: > ...which stems from the fact that the very concept of "time zone" is > somewhat ambiguous, too. Yes - I think most of us here see that. Therefore I really appreciate the flexible timestamp format Ihor suggested. > If you really want to have fun with this (and this thread hasn't >

Re: [POLL] Proposed syntax for timestamps with time zone info

Ihor Radchenko writes: > [2023-03-29 02:30 @Europe/Berlin] is special. I think you mean [2023-10-29 02:30 @Europe/Berlin]. :) -- Until the next mail..., Stefan.

Re: [POLL] Proposed syntax for timestamps with time zone info

writes: > 2023-03-23 02:30 @Europe/Berlin refers to /two/ points in time, thus > it /is/ ambiguous. As far as I understand the definitions, the point in time "2023-03-23 02:30 @Europe/Berlin" is clearly defined as 2023-03-23 02:30 UTC+0100. A bit more problematic would be "2023-03-26 02:30

Re: fontsets

Juan Manuel Macías writes: > [1] I have to add, by the way, that MatchLowercase is not always a > panacea. Hmmm... maybe add optional extra config/output option to the fontset, like so: ┌ │ ;; Fonts │ ((myfonta . ((pdflatex . "etc.") (lualatex ...) (html ...) ...)) │ (myfontb ...) │ ...)

Re: [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...")

Juan Manuel Macías writes: > 1. There could be a defcustom, something like 'org-latex-use-fontspec' > (I would vote for nil by default). I would vote to activate this by default. > (format > \\usepackage{iftex} > \\ifpdftex > \\relax > \\else > \\usepackage{fontspec} >

Re: [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...")

Ihor Radchenko writes: > But can someone check if Free* fonts are available on Windows and > Mac by default? I just checked TeXLive (on MacOS, but should be the same on all systems): The Free* fonts are part of TeXLive as truetype and as opentype versions (and partly in other formats). For

Re: insert automatically a reference to a section header and a link

Uwe Brauer writes: > Yes, but, what do you do, if you have a 10 header and each has 20 > subheaders. I avoid writing such complex documents for the moment. :) [Some custom functions] > Thanks but this did not work! Sorry. The code is meant as an inspiration, not to be used out-of-the box. I

Re: insert automatically a reference to a section header and a link

Juan Manuel Macías writes: > In Org 9.5 there is a new variable `org-latex-reference-command'. Thanks for the reminder! I once read about it, but forgot to use it after upgrading to 9.5. :) -- Until the next mail..., Stefan.

Re: insert automatically a reference to a section header and a link

Uwe Brauer writes: > I am not following you. You insert a header as in > * Intro > Now you want to refer to it with a link > As we have seen in section ... > So what precisely are you typing? I type "As we have seen in section [[*Intro]]" (literally, I tend to not use any keybindings or

Re: insert automatically a reference to a section header and a link

Uwe Brauer writes: > I wonder why this was not implemented or asked for. Hmmm... for me, the default way to link to headings is just fine, I seldom need more control over the generated labels: #+begin_src org ,* Intro Lorem ipsum dolor sit amet... ,* Another section As seen in

Re: [PATCH] Don't fill displayed equations

Max Nikulin writes: > On 03/10/2021 00:51, Tom Gillespie wrote: >> I guess one thing I'm missing/not understanding is when/why people >> want to use \[ \] instead of full #+begin_export latex block? > For example, because document without equations may become almost > useless in the case of

Re: [Question] A single *-language-alist in ox-latex.el?

Juan Manuel Macías writes: > Well, if I'm not mistaken, the situation in the LaTeX ecosystem is > this: Polyglossia appeared as a babel replacement for XelaTeX and > LuaLaTeX, since babel, at that time, had no support for these two > new Unicode based TeX engines. And, as far as I remember,

Re: Org syntax: \[ \] as block element instead of inline object

Max Nikulin writes: > I like Timothy's idea that \[ \] markup should behave like > block-level element rather than inline object. On the other hand, we will loose the ability to inline small parts of math, that should be typeset as separate equation, like: ...text \[ 1+2=3 \] more text...

Re: [PATCH] Don't fill displayed equations

Nicolas Goaziou writes: > Also, I don't think LaTeX treats it as a block element. > E.g., > > text > \[1+1=3\] > text > > is a single paragraph in LaTeX. Yes and no. LaTeX is a bit more complex and does not only see inline or block elements. It has paragraph mode (and inner

Re: [PATCH] Accept more :tangle-mode specification forms

Timothy writes: > Thank you for considering potential security implications BTW: Security-wise I would argue to even forbid the integer case. From my view next to nobody uses and is used to the decimal codes of file modes. So this decimal integer representation is the most error prone, I would

Re: [PATCH] Don't fill displayed equations

Nicolas Goaziou writes: > Now, if you want to discuss changing syntax for \[...\] and make it > a block element I wonder, why it is not a block element. As far as I know, the only difference (even in the context of Org) between \(...\) and \[...\] is, that the former denotes inline math and the

Re: LaTeX export: grffile is a stub package

Timothy writes: > meedst...@teknik.io writes: > Oh, that reminds me, we can also get rid of texcomp. > Hmmm... one note about xcolor in your list: Some configuration options are load-time options that have to be set

Re: [Worg] Proposing a few CSS changes

Timothy writes: > I don’t think a completely spartan page is entirely sensible though. Indeed! I did not want to argue for all or nothing. :) But font and font size for big chunks of text are quite important and individual choices. So the rest of the styling should try to be flexible enough to

Re: [Worg] Proposing a few CSS changes

Adam Porter writes: > So I think it's very important to respect the user's settings, > especially for long texts and documentation (i.e. not the "home page" > parts of Web sites whose purpose is to present projects as a whole). +1. HTML pages are neither books nor PDFs nor advertising columns.

Re: org-cite: how to include a cite with no key?

John Kitchin writes: > Who is to say why someone would bother. It is a command on page two > of http://tug.ctan.org/macros/latex/contrib/natbib/natnotes.pdf that > one can use. Hmmm... but I would say that the natbib command \citetext is more a helper/workaround for the missing prefix/suffix

Re: org-mode export to (latex) PDF

Jean-Christophe Helary writes: > Since org uses Latex to achieve export to PDF, which is quite a > common demand nowadays, something that normal org users can > understand should be posted somewhere. I second that! I just wanted to try to lower the expectation that (most) scripts will work out

Re: org-mode export to (latex) PDF

Maxim Nikulin writes: > Do Unicode TeX engines support such combination of fonts? Yes, they do. My rather long response was due to my impression that you are quite surprised that not everything is supported with the default configuration as you expected. I wanted to highlight that it is even

Re: org-mode export to (latex) PDF

Maxim Nikulin writes: > There are cm-super fonts for at least of 15 years. There are many tradeoffs in many aspects. No single font pleases everyone. So you want to say: Your requirements are more important/common/stylish/whatever that the requirements of other people? I do need only latin

Re: org-mode export to (latex) PDF

Maxim Nikulin writes: [utf8x] > Maybe, I have seen such warnings. However I have tested neither utf8 > nor utf8x on real examples. That is why I am unaware what can be > broken in particular. For small examples with various symbols > outside of ASCII, utf8x may give better support. The main

Re: org-mode export to (latex) PDF

Maxim Nikulin writes: > (add-to-list 'org-latex-inputenc-alist '("utf8" . "utf8x")) Do not do this. Both, utf8x and ucs, are obsolete and deprecated for quite some time. For proper unicode support, switch from pdflatex to lualatex or xelatex. With these newer backends (and proper adjustments

Re: A requires/provides approach to linking source code blocks

Marko Schuetz-Schmuck writes: > I would find it useful to have a more declarative way for specifying > sequence. I imagine e.g. using "#+REQUIRES:" and "#+PROVIDES:" to > capture dependency and then have the exporter compute a sequence > satisfying these. I would say that declaring an explicit

Re: suggestion to change default org-latex-pdf-process to latexmk

Colin Baxter writes: > I really don't understand why the changed is needed. The upcoming citation support needs a reliable way to run the required bibliography processor (e.g. biber or bibtex). Therefore the current default setting that only runs latex three times does not suffice. On the

Re: suggestion to change default org-latex-pdf-process to latexmk

Scott Randby writes: > (1) Which one of the above suggestions should I use? I don't want > interactions when I'm exporting. I don't want to have to mess with a > configuration file either. > (2) How many shell commands will org-latex-pdf-process need? Right > now there are three. Replace those

Re: suggestion to change default org-latex-pdf-process to latexmk

Tim Cross writes: > One reason is that latexmk is not installed on some systems. Just after starting to write that this is false nowadays I realized you are right. :) See: https://mg.readthedocs.io/latexmk.html For macOS latexmk is distributed with the default TeX installation MacTeX for

Re: suggestion to change default org-latex-pdf-process to latexmk

"Bruce D'Arcus" writes: > Here's the current command for the "latexmk" option: > "latexmk -g -pdf -pdflatex=\"%latex\" -outdir=%o %f" > ... and here's what you have, minus shell-escape. > "latexmk -f -pdf -%latex -interaction=nonstopmode -output-directory=%o %f" The option

Re: [wip-cite-new] Initial implementation of `csl' citation processor

Nicolas Goaziou writes: > By default, no export processor is selected. All citations are > removed from output, and print_bibliography keywords, ignored. As I'm coming from LaTeX and have been bitten more than once by missing citations in the output (which is solved far better today by

Display ellipsis at end of headline instead of after tags

Hi. I would prefer to see headline ellipsis always at the end of the headline, but if tags are present, the ellipsis is drawn after the tags. So currently I have something like this: #+begin_example ,* Headline One... ,* Another Headline :tag:another:... ,* Third Headline...

Re: Microsoft Excel spreadsheet editing directly from within emacs.

Jean Louis writes: > You speak of a programming language and what is possible with > programming language. That's not the point. Org table is integrated with Calc and Calc is a Computer Algebra System. That is something like Excel combined with Mathematica (with a little less GUI stuff) - that

Re: Microsoft Excel spreadsheet editing directly from within emacs.

Jean Louis writes: > I find Org tables useful for small reports. Just as table mode is > also useful within Emacs. Org tables are primitives that are not > comparable to spreadsheet software. It might be a difficult question, whether Org tables are the best solution in a given situation or

Re: Changed list indentation behavior: how to revert?

"Dr. Arne Babenhauserheide" writes: > Sad story short:... I'm with you - last weekend I upgrade my OS and had quite some trouble to get everything working again and still have some nasty hoops to jump through. But on the other side: What are we talking about? Org had a given default

Re: New website - back to the old unicorn!

TEC writes: > This seems very suspicious for one reason. I cannot see "Canvas" > anywhere in the entire codebase of the website, or any loaded > resources. So I have no idea where on earth the JS you're finding > has come from - I'm guessing it's improperly injected by a > extension. FWIW I also

Re: New website - back to the old unicorn!

Hi. Thanks for your great work and the wonderful new page! A minor detail: I use the plugin "Decentraleyes" and with this activated there is quite a bit JavaScript garbage at the end of the page (below the "Created by" footer). The part below the footer is this: #+begin_src js { const iframes =

Re: The Website Revamp: The final stretch

TEC writes: > 2. Picking the best 'Hero banner' on the home page :: I like Variant 1-1 the most - all other variants are a bit too big and yelling for my eyes. Maybe use size and layout of Variant 1-1 with colors of the last variant (page 9, gray background)? -- Until the next mail...,

Re: basic org questions

"Thomas S. Dye" writes: > There are many pieces of software that will allow the user to the > violate best typesetting practices easily. LaTeX is not one of them. Not quite right. I have seen people create really ugly source code *and* ugly output with LaTeX with ease. You can create garbage

Re: basic org questions

Emanuel Berg via "General discussions about Org-mode." writes: >> #+attr_latex: :center nil :booktabs t >> | My | Columns | >> |+-| >> | 1 | 2 | >> | 3 | 4 | > "PDF file produced with errors." Sorry that I try to make more general examples that are not exactly

Re: basic org questions

Emanuel Berg via "General discussions about Org-mode." writes: > OK, but the values still ned to be specified, right? No, just use the package - it sets the relevant lengths to change the style of marking paragraphs and tries hard to also reset every other length that depends on the original

Re: basic org questions

Samuel Wales writes: > for my part, i appreciate your using the "wrong" style for your > email message A plain text document presented in a monospaced font is quite a different thing than a (longer) PDF with a plethora of layout and micro-typographic options. Do you also appreciate the

Re: basic org questions

Eric S Fraga writes: > #+latex_header: \setlength{\parindent}{0pt} > #+latex_header: \setlength{\parskip}{\baselineskip} Better use #+latex_header: \usepackage{parskip} as this package has less bad side-effects on other parts of the document than setting these far-reaching lengths directly.

Re: "text mode" org mode

Emanuel Berg via "General discussions about Org-mode." writes: > Thanks, I wonder tho if all this > (setq org-descriptive-links nil) > (setq org-hide-emphasis-markers nil) > (setq org-startup-folded'showeverything) > is implied, with `visual-mode'? Beware: =visible-mode=

Re: basic org questions

Emanuel Berg via "General discussions about Org-mode." writes: > Tim Cross wrote: >> #+latex_class: korma-article > user-error: Unknown LaTeX class ‘korma-article’ >> #+latex_header: \setlength{\parindent}{0pt} > Yes, that's removed the indentation but didn't insert > a blank line... First

Re: basic org questions

Hi. Details about Org tables are to be found in the manual at different places (maybe not optimal, but that's the current structure). First of all, aspects of tables inside Emacs and Org are discussed here: https://orgmode.org/manual/Tables.html#Tables But everything about exporting

Re: "text mode" org mode

Emanuel Berg via "General discussions about Org-mode." writes: > Stefan Nobis wrote: >> (setq org-link-descriptive nil) > I don't have org-link-descriptive, it seems... No problem, the old name is =org-descriptive-links= (this name has been deprecated in Org 9.3, b

Re: "text mode" org mode

Emanuel Berg via "General discussions about Org-mode." writes: > Can I tell Org mode to don't change editing back and > forth, also don't collapse items in and out, i.e. > virtually text mode I did not test it to every detail, but the following two settings may be a good starting point:

Re: org-time-stamp in German or Spanish or....

Uwe Brauer writes: > But it still inserts <2020-09-06 Sun> What's the value of `system-time-locale'? In a shell (like Bash), is there a difference between the following two commands: #+begin_src bash LC_TIME=C date #+end_src #+begin_src bash LC_TIME=de_DE date #+end_src -- Until the next

Re: org-time-stamp in German or Spanish or....

Uwe Brauer writes: > But is inserts the name of the days in English The format and language of the time-stamps is controlled by the function format-time-string (the docstring of this function shows all the available placeholders, including "%a" for the locale's abbreviated name of the day of

Re: issue tracker?

Detlef Steuer writes: > I would go as far as saying *this list* is one of the fastest > reacting amd friendliest communities I have been part of. The job > Nicolas does is just awesome. +1! -- Until the next mail..., Stefan.

Re: wip-cite status question and feedback

Joost Kremers writes: > I don't think it's necessary to use a dash (or any other character) > in longer cite commands, though. =citeintext= isn't that much more > difficult to read than =cite-intext=. (Biblatex does just fine > without dashes, and there's always camelCase if you're so inclined.)

Re: wip-cite status question and feedback

Nicolas Goaziou writes: > Alphanumeric suffix provides 62 combinations, which should hopefully > be enough for any citation back-end out there (I'm looking at you > biblatex). It's not terribly readable, tho, as you point out. I second that. Some of the many BibLaTeX commands are due to

Re: Bug or not a bug? dot expansion in ob-shell

Bastien writes: > I agree we should have a discussion on whether :results value is a > good default. What about a third collection option 'none' and make this the default? This would emphasize that there is no sensible default for all babel languages, users and use cases. Users would be forced

Re: emacs build command for org-files

John Kitchin writes: > Hi everyone, > This is only semi-on-topic. I am looking for something like M-x compile for > my org-files, but I don't want it to necessarily use Makefiles. I am > looking for suggestions of existing solutions to this, or thoughts on how > to implement this. This may not

Re: very strange LaTeX error

"Fraga, Eric" writes: > However, it seems that simply adding \relax does not work if there > is an \hline immediately following so the solution is not that > straightforward. Hmmm... but it should be solvable. Maybe something along the lines of this (rough sketch, I have next to no experience

Re: very strange LaTeX error

"Joost Kremers" writes: > The solution I usually opt for is to enclose the brackets in an > additional set of braces: `{[...]}`. Whether Org export can and > should automate that, I can't say. In the generated LaTeX adding a '\relax' (so each line ends with '\\\relax') would be a another

Re: Finally figuring out some ob-sqlite stuff -- for worg?

Eric Abrahamsen writes: > I was confused in part because the "where exists (select *..." looks > like its main purpose is to return rows. Indeed that's the purpose: Restrict the set of rows upon which update acts on. Here I tried to reformat the statement a bit in order to emphasize its

Re: Finally figuring out some ob-sqlite stuff -- for worg?

Eric Abrahamsen writes: > Okay, it's up. If anyone wants to explain to me the point of the > "where exists" clause in the SQL, I would be interested to hear. It > works as expected this way, but is that clause necessary? Yes, very necessary. Without it, all ratings would be changed - the two

[O] Clocktable creates superfluous columns

Hi. In version 9.0.5 Org (Emacs 25.1) seems to generate too many columns in some situations. I'm not quite sure since which version this happens, in Org 8.x I have not seen this behaviour. Here is a small example: --8<---cut here---start->8--- #+BEGIN:

Re: [O] Clocking work time vs. office time

Marcin Borkowski writes: > No, you're not - this is one possible solution. I'm curious about other > ones. If tracking the time you're at a specific location is your main objective (and if you own a Smartphone), I would say: Geofencing. Let your Smartphone track when you

Re: [O] using vref in latex export, and normal links in html export

Alan Schmitt writes: > I'm converting a latex document into org-mode to easily export it both > to latex and html. I've just encountered something that I don't know how > to do: export a \vref reference. I would like to have something that > exports to \vref in

[O] Bug in table formular - last column specifier broken

Hi. With the last update to Org-mode version 8.3.2 (8.3.2-48-g700b8e-elpaplus) the following table formular breaks: --8<---cut here---start->8--- | | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Sum |

Re: [O] Merge branch 'maint'

Oleh Krehel writes: > Would it be so hard for Git to perform a single merge of master into > maint on release, while keeping them separate and cherry-picking > in-between for the sake of a clean linear history? The question is not whether git is capable of doing this (there

Re: [O] Babel and R: Call code block and output plot

Andreas Leha andreas.l...@med.uni-goettingen.de writes: You still have to specify the format of the results of the #+CALL line, as in #+CALL: myplot[:exports results]() :results file Works like a charm, thank you very much. -- Until the next mail..., Stefan.

[O] Babel and R: Call code block and output plot

Hi. I'm playing a little bit with R code blocks in babel and calling them in different parts of my document (e.g. showing output in the main part and the code in the appendix). With most code blocks (e.g. setting some variables or outputting a LaTeX table with xtable) this works as expected

Re: [O] org-mode to latex, again!

Marcin Borkowski mb...@wmi.amu.edu.pl writes: As I wrote - yes, provided you update the filename database (e.g. launching mktexlsr from the command line). (Because of speed, TeX does not search the directory tree each time it looks for a package or something, but uses a database in a

Re: [O] [OT] A short (less than a minute), informal survey about LaTeX

Marcin Borkowski mb...@wmi.amu.edu.pl writes: 1. Did you know about the savetrees package by Scott Pakin Yes. 2. Would you find it useful when producing PDF files other that scientific articles (using Org-mode or not)? No. I use org-mode mostly for documentation and even documentation

Re: [O] fontenc makes pdf non-searchable

Martin Leduc mart...@hotmail.com writes: You can find a minimal example here[1], with the org file, and the tex and pdf files generated from it. Firts try to search within the pdf. It does not work (at least on my side) To solve the problem, remove the line with \usepackage[T1]{fontenc} Your

Re: [O] fontenc makes pdf non-searchable

dbo...@mmm.com (J. David Boyd) writes: And how did you determine that please? I assume you mean how I determined that the PDF has been produced by dvips and Ghostscript. In this case: I've just looked into the document information of the PDF file. For example with Acrobat Reader I just press

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: By saying bibtex is not a requirement, I said exporting to bibtex. You talked about Zotero but showed a bibtex entry. Therefore exporting from Zotero to bibtex may not be a requirement, there may be a direct interface to Zotero,

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

t...@tsdye.com (Thomas S. Dye) writes: It strikes me that basing core features of the citation syntax on the software users happen to be using today is a bit like this--at some point the design of the system will prove unprepared for new developments. I don't think this is a big problem. We

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes: On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote: IMHO keys with lots of ??? in them are a sign of a data problem. Therefore the author should solve the root cause. Not in the specific case that I cited. The Bib entry

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Richard Lawrence richard.lawre...@berkeley.edu writes: Like I said, this seems like an edge case, and I don't see that it is necessarily Org's responsibility to accommodate the keys produced by Zotero in such edge cases. And there is a significant benefit to *not* accommodating such keys:

Re: [O] Citation syntax: a revised proposal

Aaron Ecay aarone...@gmail.com writes: I count roughly 50 commands in sections 3.7.1 – 3.7.6 of the biblatex user’s manual (version 2.9a of 24/06/2014). Some of these are quite esoteric, of course, but they are all provided. There are many commands (and even more private commands are

Re: [O] Citation syntax: a revised proposal

Richard Lawrence richard.lawre...@berkeley.edu writes: 1) Is it worth allowing a name for a user-defined type in the [cite: ...] part, or is it OK to confine user-defined types to the second part (like: [cite: ...] %%(:type foo) or [cite: ...]{:type foo})? IMHO it is better to have such an

Re: [O] Citation syntax: a revised proposal

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes: From what I read in this and the previous thread, the new proposal tries more or less to reimplement BibTeX in org. No, that's wrong, not the database should be replaced. The goal is to make citations a first class citizen in the

Re: [O] Citation syntax: a revised proposal

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes: I see, so in the examples provided Doe99 is only the key, org would not have to know that the author name is Doe and its year is 1999, or any other information about the citation. Yes and no. In the first place org should only

Re: [O] Citation syntax: a revised proposal

Richard Lawrence richard.lawre...@berkeley.edu writes: Rasmus ras...@gmx.us writes: Parts I hate: The flag is either `@' or `'. `@' [...] The optional hyphen (`-') Too many weird symbols that I won't be able to remember, much less explain to somebody else. I don't love these

Re: [O] Citation syntax: a revised proposal

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Time for another crazy idea. Last one on my side for today [cite ...] [(cite) ...] [Cite ...] [(Cite) ...] It should solve the :capitalize issue. +1 I really like it - even when looking at the org file with something weird like vim, it's

Re: [O] Colon in block name?

Loris Bennett loris.benn...@fu-berlin.de writes: The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'. But you attached it as inline, so the same problems could arise. To be sure to transfer the file unmodified, choose attachment as disposition. Reading with Gnus, I don't see

Re: [O] Citations, continued

Richard Lawrence richard.lawre...@berkeley.edu writes: I know these commands are convenient, and that not having them would introduce this class of errors, but the question is whether they are so important that it's worth providing an equivalent for them in non-LaTeX backends. Hmmm... I

Re: [O] Citations, continued

Richard Lawrence richard.lawre...@berkeley.edu writes: Rasmus ras...@gmx.us writes: Citation types for extracting parts: citeauthor, citetitle, citeyear, citedate, citeurl, As I've said in other posts, I think maybe we should not think of these as `citation' commands and thus don't

Re: [O] Include another org-document without settings

Nicolas Goaziou m...@nicolasgoaziou.fr writes: You can skip the first lines of an INCLUDEd file with :line parameter. You can also only include a section. See manual for details. Thank you for the hint. I used something like #+INCLUDE a.org :lines 3- but still got duplicate keywords (the

[O] Include another org-document without settings

Hi. I try to build an org document that has two parts. One file contains the first part of the resulting document and should be useable stand-alone. The second file is some kind of extension to the first file. My idea is to simple #+INCLUDE the first file in the second one. But then the global

Re: [O] Include another org-document without settings

Eric S Fraga e.fr...@ucl.ac.uk writes: When I used to do this in LaTeX, I usually had a /master/ document which included the others. That's what I did with pure LaTeX, too. But then there is the nice feature in AucTeX which allows you to compile the whole document while you are in one of the

  1   2   >