Ihor Radchenko writes:
> AFAIU, source block switches are never inherited.
>
> Dear All, may we should provide a normal header arg as an equivalent of
> switches? Honestly, this whole switch syntax sounds unnecessary and only
> over-complicates things.
I think that web pages or documents that
Max Nikulin writes:
> On 19/07/2022 22:01, Juan Manuel Macías wrote:
>> + (replace-match
>> + (mapconcat (lambda (option) (if (equal "AUTO" option) language
>> option))
>> + (cond ((member language options) (delete "AUTO"
Fraga, Eric writes:
> I really do not understand the last paragraph although it implies that
> org already supports adding the line numbers. My elisp-fu is not up to
> scratch to figure this out from the code unfortunately. Would somebody
> explain what to do? Or should I simply add the CSS
Here is a new version of the patch, with the fixes added.
Important: I have modified in this patch org-latex-guess-babel-language
so that it recognizes the new Babel syntax alongside the old syntax.
That is, it is now possible to put:
#+LaTeX_Header: \usepackage[arguments,AUTO]{babel}
Uwe Brauer writes:
> Regards (take care with the heat if you live in Spain (not sure though))
Yes, I live in the Sierra de Madrid, where we are always a few degrees
below Madrid, and these days this is an oven. I guess that you are also
in Spain, because of the mail from the UCM. If so, take
Uwe Brauer writes:
> Now if I want to switch to the convention used in Germany (that might be
> relevant if I want to export it later to csv, but this is a different
> topic) does work in a strange way, any comments? [...]
Hi, Uwe,
If you only need to export to LaTeX you can load the siunitx
Max Nikulin writes:
> On 18/07/2022 17:32, Juan Manuel Macías wrote:
>> For example, something like this:
>> latex-lang: babel(sorbian) variant(upper)
>> provide(hebrew:import,hyphenrules=+) options(bidi=default),
>> others(french,catalan)
>> returns:
>>
Juan Manuel Macías writes:
> latex-lang: babel(sorbian) variant(upper)
> provide(hebrew:import,hyphenrules=+) options(bidi=default),
> others(french,catalan)
>
> returns:
>
> \usepackage[french,catalan,uppersorbian,bidi=default]{babel}
> \babelprovide[import,hyphenrules
Ihor Radchenko writes:
> Do you refer to the paragraph below when saying that Org implementation
> makes it hard to add new features? The rest of the above paragraph
> implies that the difficulty is on LaTeX side, not on Org side.
Sorry for not explaining clearly. Actually I think the problem is
Ihor Radchenko writes:
> For Max's comment, using plist/alist would make things more clear
> code-wise for future developers. I always find it annoying when I need
> to go back and forth checking which element should be second or third or
> forth in the list. Especially if the variable is used
Hi all,
I am writing a package for LuaLaTeX and have decided to use Org for it.
The reasons: org is more powerful, more versatile and more cool than the
'official' LaTeX literate programming utility, docstrip.
Searching for information on this list I found this post from Marcin
Borkowski, from
Max Nikulin writes:
> I would consider structures with named fields (alists or plists) for a
> case of adding some additional settings (Font name? But it is rather
> defcustom than defconst)
>
> ("es" . (:babel "spanishmx" :poliglossia "spanish"
> :poliglossia-variant "mexican")
I was paying
Max Nikulin writes:
> I have tried on Ubuntu-20.04 LTS focal (Latest LTS is 22.04 jammy).
> Without explicit fontenc it may work, but emits a warning
>
> Package babel Warning: No Cyrillic font encoding has been loaded so far.
> (babel)A font encoding should be declared before
Hi, Marcin and Samuel, thanks for your comments,
Marcin Borkowski writes:
> You might want to extend it and create a minor mode which would display
> data about the current character in the echo area, Eldoc-style, or in
> a tooltip when you hover the mouse pointer over a character. Depending
>
Juan Manuel Macías writes:
> In any case, I personally think that org-latex-language-alist, as it is
> now in this patch, is sufficient.
By the way, Maxim. I have been doing some tests with pdfLaTeX. I've
known for a while now that it's no longer necessary to load the inputenc
p
Max Nikulin writes:
>> Subject: [PATCH] * lisp/ox-latex.el: New variable `org-latex-language-alist'
> Writing the previous message I forgot that currently there is no
> default option for the fontenc package (PdfLaTeX), e.g. T2A for
> Cyrillic. As a result it is not enough to specify just
Ihor Radchenko writes:
> Thanks!
> This looks like an improvement.
> However, we may need to preserve the old defconsts for the time being
> and declare them obsolete.
Hi, Ihor,
I attach the new version of the patch with both variables declared
obsolete.
If everything is ok, I can add what is
Sorry for the slight offtopic.
Since Unicode and character issues come up here from time to time, I'm
sharing this 'homemade' function that I wrote a long time ago for my
work, in case someone finds it useful. It Shows a brief descriptive list
of all characters in a word at point. Each character
Stefan Kangas writes:
> If that is true (I don't know) then maybe we should just use a more
> ubiquitous glyph?
I have done a quick test with some fonts that are ---I believe--- quite
popular. This character is missing from DejaVu Sans Mono, Iosevka,
Source Pro, Fira Code and Hack. JuliaMono
Juan Manuel Macías writes:
> The most reasonable thing would be to use a more
> common symbol. But I'm still intrigued by the origin of that symbol...
It seems that the culprit is in line 1592 of org-agenda.el
I think this should be considered a bug, since the glyph used (LEFTWARDS
TR
Hi, Daniel,
Daniel Ortmann writes:
> – Would using the ASCII '<' character be a better solution?
I've done a quick test and a few very popular (and more or less
complete) fonts don't include a glyph for the LEFTWARDS TRIANGLE-HEADED
ARROW #2b60 character: DejavuSans, Iosevka, Hack Source Code
Hi,
Daniel Ortmann writes:
> Any clues where this particular symbol resides? A hint about the
> package name would wonderful. :-)
To be able to display "unusual" symbols in Emacs, I usually use the
symbola font:
You can download it here:
https://fontlibrary.org/en/font/symbola
And then:
Today I discovered that luaotfload included in v. 3.12 a new
experimental function, luaotfload.add_fallback, to be able to add a list
of fallback fonts to a LuaTeX document, at a low level.
(More info on page 18 of the luaotfload manual, with some examples).
I've been experimenting a bit with
Stefan Nobis writes:
> Hmmm... maybe add optional extra config/output option to the fontset,
> like so:
>
> ┌
> │ ;; Fonts
> │ ((myfonta . ((pdflatex . "etc.") (lualatex ...) (html ...) ...))
> │ (myfontb ...)
> │ ...)
> │ ;; Fontsets
> │ ((myfontset .
> │ ((sans . myfonta)
> │(serif
Hi, Timothy,
Timothy writes:
> Yep, so in my config’s implementation I have an alist of fontset names and
> individual fonts. For something part of org-mode itself, we’d probably want to
> add a format level to this, something like:
>
> ┌
> │ ((fontset-name .
> │ ((serif .
> │
Timothy writes:
> As an illustrative example, if I include this in one of my documents and
> create
> a PDF:
> ┌
> │ #+options: fontset:biolinum
> └
>
> Then I’ll get text with:
> ⁃ libertine roman as the serif font
> ⁃ biolinum as the serif, and default, font
> ⁃ source code pro as the
Max Nikulin writes:
>> \\relax
>> \\else
>
> Is it the case of latex as the old engine with tex->dvi->ps workflow
> besides new XeTeX and LuaTeX? However such engine is not used by Org.
According to the iftex documentation (p. 2):
\ifpdftex, \ifPDFTeX
True if PDFTEX is in use (whether
Tim Cross writes:
> Juan, if I understand your proposal correctly, I think your on the right
> track. It sounds like what you are proposing would have almost no impact
> on basic users like me, but would allow those with more demanding
> requirements to adjust without too much effort. I
Juan Manuel Macías writes:
> By the way, although I've already commented on it in some post in the
> parent thread, i think this package I wrote might be useful for doing a
> quick visual test of a font (including opentype features test), using
> org-latex-preview (compiling with Lua
Stefan Nobis writes:
> 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.
I voted nil because of the available fonts issue. But I
Sorry, I forgot to add quotes :-) "\\usepackage{iftex}...\\fi"
Juan Manuel Macías writes:
> (format
> \\usepackage{iftex}
> \\ifpdftex
> \\relax
> \\else
> \\usepackage{fontspec}
> \\usepackage{unicode-math}
> \\defaultfontfeatures{Scale=MatchL
Considering some discussions in the parent thread, I think maybe it
wouldn't hurt to ensure a minimal preamble when the output is compiled
with LuaLaTeX or XelaTeX, so that some very basic fontspec configuration
is loaded to be able to read PDFs in non-Latin scripts.
But before proposing the
Tim Cross writes:
> Thanks Juan. It will be fairly trivial to compile the information you
> have provided into a basic org document which I can then add to org. If
> on the other hand you would prefer to write it up, all I need is an org
> document which is based on the (current) org 'worg'
Max Nikulin writes:
> Characters from Latin scripts, the set is wider than latin-1 but does
> not cover other languages. I do not dispute that font encoding is
> Unicode (if it can be stated so), usually support of Unicode is
> associated with smooth experience with wide range of languages.
A
Max Nikulin writes:
> LuaTeX uses Latin Modern
> and it is not nearly Unicode
Maxim, please look at this screenshots carefully:
https://i.imgur.com/uMfheCL.png
https://i.imgur.com/WwGybBA.png
https://i.imgur.com/hpreFNQ.png
Frankly, I don't know what Latin Modern you're referring to, and
Hi, Gerardo,
Gerardo Moro writes:
> As for your own package, Juan Manuel, I understand the main purpose is
> to take screenshots of movies. Am I correct?
> Thanks!
Yes, it is a series of homemade hacks (if i called it "package" I would
sound too presumptuous lol), just to be able to take
Hi Thomas,
Thomas S. Dye writes:
> Yes, what I called Babel you call org-babel. I don't know if the Lua
> handler of source blocks in Org might be useful for someone interested
> to write Lua extensions to LaTeX.
I'm writing a package for LuaLaTeX in Org[1] using lua code blocks, and
Hi, Maxim,
Max Nikulin writes:
> [...] With LuaTeX you get more convenient OTF and TTF font selection, but
> you you have to pay for the feature. It is necessary to explicitly
> specify all families: normal, typewriter, italics, etc if you need
> Unicode. -
Not necessarily. You can go from the
Hi, Tim, thank you for your comments,
Tim Cross writes:
> Juan, I think it would be great to add your post to worg. I'm happy to
> do this, but I think it wold also be good if we could include a basic
> 'setup' i.e. what changes people might need to (or should do to maximise
> benefit) in order
Bruce D'Arcus writes:
> Today, I think the only advantage pdftex has is speed; it's a lot
> faster to compile documents than luatex.
That's true, but it seems to be a LaTeX and fontspec issue. I think
ConTeXt, which uses LuaTeX, is faster, but I don't have the hard data.
In general TeX is slow
Hi Uwe,
Uwe Brauer writes:
> Thanks for that list.
>
> Well I have felt in the past the same about pdftex, but I have partially
> switched to xetex precisely on the reasons you list.
>
> I have not have the time, to really try out Luatex. Did you have the
> time to compare it with XeTeX?
First
Gerardo Moro writes:
> Hi,
>
> I recently discover the Obsidian Media Extended plugin
> (https://www.youtube.com/watch?v=GQXVWtNkeZw) to take notes while
> watching videos / listening to audios with keybindings to stop the
> video and create timestamps with link to the specific moment of the
>
TL;DR: A list of use cases where using LuaTeX is more advantageous than
using pdfTeX
Many times Org users who frequently need to export their documents to
LaTeX, but who do not have much LaTeX experience (or their knowledge of
the TeX ecosystem is somewhat out of date), find
Ihor Radchenko writes:
> This capture template is public: https://github.com/yantar92/org-capture-ref
Thank you! It is very complete, and I have seen that it also integrates
with qutebrowser. I'll try it as soon as I have time.
Best regards,
Juan Manuel
arthur miller writes:
> This one draws graph of cons cells (lists):
>
> https://github.com/amno1/draw-cons-tree
>
> I never tried with random s-expressions, but I guess you could pass
> them in as lists?
Hi, Arthur,
Thank you for the pointer to draw-cons-tree. I didn't know this package,
I'll
Ihor Radchenko writes:
> Invoking search across my notes and archives (all stored in Org, of
> course) yielded the following:
>
> https://reddit.com/r/emacs/comments/u2ca5c/drawtreeel/
> https://reddit.com/r/emacs/comments/kzeyun/pairtree_a_learning_tool_for_visualizing_elisp/
>
> linking to
>
>
Hi all,
Sorry for the slight offtopic. I'd like to be able to graphically
convert (from a src block) a Lisp expression to a tree diagram, similar
to trees used in (human) syntax and grammar, especially generative
grammar (this is a web app for generating such trees:
Sébastien Gendre writes:
> If I learned LaTeX syntax in the past, I never take enough time to learn
> how work each compilation possibility. I feel lost with all the
> pdflatex, teklive, lualatex, double or quadruple compilation, etc.
The problem of multiple compilations is not related, in
Hi, Sébastien,
Sébastien Gendre writes:
> To generate the table of contents, I have to compile my .tex file into
> PDF 2 times. The first time, I got no toc. The second time the toc was
> here.
I would say It's a normal LaTeX thing. Sometimes LaTeX needs more than
one compilation to finish
Tim Cross writes:
> As I understand it (which isn't brilliant), the core problem is more to
> do with how the LaTeX/TeX engine processes the input to generate the
> postscript and pdf output. Modern PDFs have a wealth of internal tagging
> which simply sin't supported via the tex -> pdf pathway.
Hi, Robert,
Robert Weiner writes:
> We do like avy and as you say, Hyperbole can work with it. We try to
> avoid requiring any non-builtin Emacs packages for Hyperbole. With a
> few, we support them optionally. Unless there is a strong use case
> for utilizing avy in certain ways, we would
Hi all,
I know some old school LaTeX users who are interested in giving Org a
try, but seem to have a hard time getting out of their LaTeX comfort
zone. So I thought maybe it wouldn't be a bad idea to invite them to try
some Org doses without leaving LaTeX. I got the idea from the LaTeX
markdown
Hi, Robert,
First of all, welcome to the list. And of course congratulations on all
the great work you've done with hyperbole. In my ignorance, when I
recently installed it from ELPA, I thought it was a relatively recent
package. But it seems that you have been developing it for a long time,
Hi Jonathan, sorry for my late response,
indieterminacy writes:
> I recommend Hyperbole, though I must confess Ive been using Orgmode a
> lot less since Ive been focusing on the format GemText.
>
> I should recommend the use of the function defil, for people who like
> regexes and want to
Hi David,
David Masterson writes:
> I haven't touched Hyperbole in ...decades...? Even then, it was
> complicated and full-featured (but I still keep it in my .emacs file).
> My discussions with Bob Weiner were interesting at the time and I really
> wanted to make use of it.
>
> As you've
Max Nikulin writes:
> If alternative text for images and description of
> links are not convincing [...]
It does convince me, Maxim, that's why I told you in my previous message
that you were right in that example you had put about the alternate
text. And my question was (and still is) if you
Hi all,
Thank you very much for your comments and contributions in this thread
about Org & hyperbole, which have helped me a lot to position myself.
Certainly, for the short time I've been using hyperbole, it has me
baffled. It's like someone grabbed all the tools that could be useful
ten
Max Nikulin writes:
Hi Maxim,
Max Nikulin writes:
> I would like to stress that styles can not be a rescue in some
> important cases. Let's leave aside ad hoc final tuning of formatting.
> In the case of HTML export there are still and
> attributes that are namely
> per-object, not part of
Hi,
I've been intrigued with GNU Hyperbole for a while. I'm reading the
documentation and trying it out a bit. It seems that its button system
is very powerful. But Org links are also powerful (and exportable), and
can be extended outside of Org docs. It seems that hyperbole offers some
cool
Hi, Christian,
Thanks for your comments.
Christian Moe writes:
> Hi,
>
> This makes sense to me.
>
> Note: For the html output in your example, I expect you don't mean
> contents>, but contents. That
> would give the desired custom style controle of the output, and would
> parallel the behavior
Bruno Barbier writes:
> But, you can easily define your own command.
>
> (defun my-scroll-up-of-1 ()
> (interactive)
> (scroll-up-command 1))
>
> (define-key global-map (kbd "M-n") 'my-scroll-up-of-1)
Or simply doing something like:
(define-key global-map (kbd "M-n") (lambda
To add some ideas that have been occurring to me these days...
I am more and more convinced that inline special blocks, by their
nature, should not support fine tune options or anything like
attr_latex, attr_html, etc. like its older brothers, as it would produce
an overly complicated syntax. Big
Hi all,
I’m writing an article about a movie, and I needed to get some
screenshots as image links inside Org. I know some package for those
things, like org-media-note, a nice library but for me it has two
drawbacks: it has, for what I need, too many bells and whistles; and
uses the mpv.el
Ihor Radchenko writes:
> While arbitrary markup can indeed be introduced using our current link
> syntax, there is one important limitation of links:
>
> *** link description cannot contain other links ***
>
> If one seriously tries to extend Org syntax with custom markup elements,
> nested
Hi,
Cletip Cletip writes:
> - they are made implicitly to make a "key :: value" couple, which can
> be convenient
Leaving aside typographical considerations, what LaTeX calls, for
example, "description" (because Org is totally typographic agnostic), I
find this property that you mention very
Ihor Radchenko writes:
> The original proposal by Eric Schulte:
> https://list.orgmode.org/4bffee4f.5010...@ccbr.umn.edu/
Maybe we should allow either exporting just the headlines of the
org-mode file or exporting the entire org-mode file -- possibly after an
ASCII export -- this
Ihor Radchenko writes:
> I think that the existing code can be improved. Relying on the
> undocumented behavior of (org-back-to-heading) is not ideal. Not to
> mention code blocks before first headline.
>
> It would be great if you rewrite the existing code to suite both the
> defaults and the
Hi, Rudolph,
Rudolf Adamkovič writes:
> Oh, I see. Thank you for the explanation. I can see myself using such
> new tangle comments all the time! But then, I use UTF-8 and not the
> standard 7-bit ASCII for my Org documents. Hence, I would want to see
> ':comments plain' or ':comments
Hi, Rudolph, thanks for your comments,
Rudolf Adamkovič writes:
> Juan, hi!
>
> I do not understand the meaning of ASCII. How will such comments look
> like? Will they include at least the file name? If so, those can
> contain Unicode characters, right?
The main motivation for proposing this
Hi, Ihor, thanks for your comments,
Ihor Radchenko writes:
> Wouldn't it be better to supply a customization for
> org-babel-process-comment-text instead?
>
> I do not feel that per-src-block control on the comment type makes much
> sense here.
My first approach was actually to define some
Hi,
With this new value, comments are passed to the source file as plain
text, without the org metadata (keywords, property drawers, etc.).
As usual, feedback and suggestions for this patch are greatly appreciated.
Best regards and happy weekend,
Juan Manuel
>From
Cletip Cletip writes:
> Thank you for your answer.
You're welcome.
> Your answer seems perfect to answer my question: I modify a function
> of org-mode, and it allows me to attach folders and files to a
> heading.
> Unfortunately, it doesn't work (probably because of my version of
> org-mode
Hi,
Cletip Cletip writes:
> My question is in the object : can we attach a directory to a heading?
> If yes, how, if not, why. Can we solve the problem?
I have in my init the following modification to the org-attach-attach
function so that I can copy a directory. I have replaced the line
((eq
Ihor Radchenko writes:
> The default switches syntax was originally designed for code block and
> it generally supports continuous numbering across several subsequent
> code blocks or starting the numbering from certain line. Will such
> features be useful for verses?
> [...]
> Do you know if
Ihor Radchenko writes:
> Sounds reasonable. However, a more consistent way to handle line numbers
> would be using switches, like what we do in EXAMPLE blocks. See
> org-element-example-block-parser and 12.6 Literal Examples section of
> the manual.
(I didn't remember that I had sent this
Eric S Fraga writes:
> I use drawers for this and then have specific processing of different
> types of drawers, depending on target.
>
> For instance, I might have :note: drawers (similar to inline tasks) with
> the following processing (for odt export; similar for LaTeX):
>
>
Ihor Radchenko writes:
> Yet, the information is surprisingly scattered. I was unable to find a
> single guide on the available possibilities. Mostly unanswered or
> partially answered questions from users.
Yes you're right. In addition, what I have been testing is not a panacea
either. In
Uwe Brauer writes:
> I have also to confess, that I usually am I bit hesitant to use
> defadvice since it changes the vanilla function, and might cause
> problems, but maybe this is just me.
You are absolutely right, and I confess that I would have the same
precautions :-). Also, the defadvice
Ihor Radchenko writes:
> A more advanced approach would be using
> \include + \includeonly instead of \input:
>
> https://web.archive.org/web/20160627050806/http://www.howtotex.com/tips-tricks/faster-latex-part-i-compile-only-parts/
Yeah, \include and \includeonly save the .aux files for each
Uwe Brauer writes:
> When I run it I obtain
> if: Symbol’s value as variable is void: my-latex-export-path
>
> Another point is if I decide to export it to ods, I need to modify that
> advice, but I agree the new function is more convenient.
You must add the variables to the document as local
Juan Manuel Macías writes:
> One (pedestrian) way to achieve it, with this function:
I think it can be done better this way, defining an advice around
'org-export-output-file-name'.
In your org file you should add these two local variables:
# my-latex-export-path: "~/path/to/myfile.t
Hi Uwe,
Uwe Brauer writes:
> Hi
>
> Currently I use
> #+EXPORT_FILE_NAME: /home/oub/Desktop/some-stuff.html
>
> To export my org file in html format to that location.
>
> But I would also like to export it as a latex file to a different
> location, without modifying the above line, or to be
Ihor Radchenko writes:
> I am not sure if I understand correctly. Do you mean that you only
> preview the book parts you are currently working on via latexmk -pvc?
> What kind of more control are you referring to?
The -pvc flag means that if latexmk detects any modification to any
document
Hi Ihor and Christian,
Ihor Radchenko writes:
> Christian Moe writes:
>
>> Do I understand correctly that the main advantage of this approach (over
>> #+INCLUDE) is the ability to continuously update preview of the whole
>> book with latexmk -pvc even if you only re-export one chapter from
>>
Hi all,
- tl; dr: I describe here my workflow with org-publish to work with long
books.
—
I discovered a long time ago that `org-publish' not only works very well
for managing websites but also for working with long and complex books
with many parts, with output to LaTeX/PDF. I developed a
Ihor Radchenko writes:
> I think that we might simply allow to define complex configuration
> before the containing paragraph. Something like:
>
> #+attr_latex[name]:
> Vestibulum convallis, lorem blockname_[<>]{text} a tempus semper, dui
> dui euismod elit, vitae placerat urna tortor vitae
Hi, Kaushal, thanks for all your interesting comments,
Kaushal Modi writes:
> The challenging part will be deciding the syntax so that there are no
> false matches.
>
> May be reserve "inline_" for inline blocks?
>
> e.g. inline_[options]{text} ?
It seems to me the most consistent option, if
Hi all,
I think this idea was suggested by Ihor in a thread from a few months
ago (I don't remember which one), but since other topics were discussed,
the idea remained a bit in limbo. I still find the idea very
interesting, and I think it would be very productive for Org to have a
multipurpose
Eric S Fraga writes:
> Same with me. I have to have a smartphone as our institution made the
> decision to remove all landlines and have all staff use MS Teams as our
> work "phone". I use termux to give me access to Emacs + org so that I
> at least get some real use out of the "smart"phone.
Max Nikulin writes:
> Do termux and emacs build for it have support of D-Bus or notify-send
> binary?
I'm not sure, but I would say yes, because Termux has a repository for
X11 applications and to be able to run desktop environments and
graphical applications (via VNC). But in such a case, I
Max Nikulin writes:
> Does termux have a notion of mailcap, e.g. mime-support package or
> something similar? I have a hope that
>
> application/pdf; termux-open %s
>
> in /etc/mailcap or in ~/.mailcap might be enough instead of explicit
> configuration of particular packages.
I've been
Ypo writes:
> These are my variables, it keeps changing what I have already written:
>
> '(case-replace nil)
>
> '(dabbrev-case-distinction t)
> '(dabbrev-case-fold-search t)
> '(dabbrev-case-replace t)
> '(dabbrev-upcase-means-case-search nil)
With those values it works for me as expected.
Hi all,
I have recently installed TeX live on Android inside Termux:
$ pkg install texlive-installer
(https://wiki.termux.com/wiki/TeX_Live)
And I've managed to open a PDF exported from Org using an external
android viewer (mupdf, downloaded from f-droid). The Termux command is
termux-open.
Ypo writes:
> Hi
>
> I find dabbrev and fancy-dabbrev very useful to typing fast. But there
> is a problem I am not able to solve: When I apply an expansion while
> writing, the case is always that of the expansion, I can't make it to
> respect what I have written. An example:
>
> — (Typing) "Hel
andrés ramírez writes:
> Right. It is giving me an error I have NOT noticed it because the pdf is
> being generated.
Your document is probably compiled on export with the
`-intercaction=nonstopmode' option, and thus does not break the
compilation with an error. In any case, I don't really
hi Andrés,
andrés ramírez writes:
> Hi. Juan.
> My comments below.
I'll explain what happens. There really isn't an alignment issue. TeX by
default applies a first line indent to paragraphs. It also defaults to
applying English typographical conventions, as is the case in your
document, where
Hi Andrés,
Andrés Ramírez writes:
> When I export the file M-x org-export-distpach l p
>
> The second and third paragraph do nat have right alignment as the first
> paragraph.
Can you please copy the contents of your .tex file here: `M-x
org-export-disptatch l l'?
Best regards,
Juan Manuel
Hi all,
TeX Live 2022 includes a new LaTeX package for citations,
'citation-style-language', written by Zeping Lee. According to the
package description:
"[...] The citation-style-language package is aimed to provide another
reference formatting method for LaTeX that utilizes the CSL styles. It
Hi Uwe,
Uwe Brauer writes:
> Which gets exported to verbatim not lstlisting as I want
Try adding this:
:wrap lstlisting
(I don't use matlab, but I think that should work).
Best regards,
Juan Manuel
Hi all,
In case anyone finds it useful, I'm sharing this function here that I
recently wrote, to convert a LaTeX buffer to an Elisp expression,
suitable for adding to `org-latex-classes'. It's a bit rudimentary, but
I think it does the trick. It can be useful for long preambles with a
lot of
301 - 400 of 829 matches
Mail list logo
