Re: Code blocks and quotes export style
> When I export an Org file to LaTeX and finally PDF, the code blocks and > quotes often exceed the width of the page. > Is it possible to set some style of the exported blocks ? I wonder what the export engine can do about code which is too wide? As a programmer, I certainly wouldn't like some brainless line-breaking make a mess of my beautiful code Most coding standards recommend lines at most 80 characters wide, or even a tad shorter, but this requires tiny letters, if generous LaTeX margins are used. ...not least with A4-paper. Before truly smart AI shows up, the only alternative I see is writing short enough lines manually. ...but I am no expert on Org Mode. Cheers Rasmus
Re: org-modern
Call me old-fashioned if you like, but when I see efforts like org-modern, I cannot help but thinking about Neo in Matrix. It was his ability to see the source code, which gave him his god-like powers. I therefore draw the line at (conventional) syntax highlighting. (I am painfully aware my standpoint could have its roots in the following phenomenon: You tend to take new inventions for granted, if they appeared when you were 15 years or younger. Inventions appearing between the age of 15 and 35, are not only accepted, but often hailed as "break-throughs", "game changing", and the like. Once you are older than 35, most new things tend to be dangerous, or even evil.) Cheers Rasmus
Re: [PATCH] Add support for $…$ latex fragments followed by a dash
Rudolf wrote: > Further, \(\) brings 100% more characters than $$, resulting in more noise in > the sentence. Now where did I put my APL keyboard... Cheers Rasmus
Re: Playing down the text in org-mode
Dear all, I skimmed through most of the answers, so forgive me if the following has already been said. The question triggers an old LaTeX reflex; If the layout tweak or typography tune turns out to be very difficult to accomplish with LaTeX (including all the mainstream add-ons), then the reason could be that you ask for something which most typographers consider to be a really bad idea. Maybe I use these options incorrectly, but aren't plain parentheses, '()', and footnotes, the traditional means for adding stuff which the reader can skip? The usual recommendation is to avoid using these tools too much, since they distract. This said, I would like to mention some old-fashioned typography used in (a reprint of) the sixth edition of "Hydrodynamics" by sir Horace Lamb. Some stretches of the text in it are printed with smaller font size than the bulk. First I thought these stretches contained background information, elaborations on nitty gritty details, or something of this kind. As this theory wasn't supported by the contents of these harder to read sections, I struggled to come up with a good explanation. My current guess is that this book was produced so long ago that the publisher and author could not afford the luxury of producing new page breaks for the later editions of the book. In order to fit longer explanations into the narrative, the text just had to shrink a bit. The first edition was published 1879, the sixth 1932, and Knuth was born 5 years later. Another unusual feature is that the book makes do without figure and table numbers and captions. Each table and figure has been placed "in context", and you will just have to read the text to learn about them. Cheers Rasmus
Re: Org-syntax: Intra-word markup
Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, December 2nd, 2021 at 4:24 PM, Robert Pluim wrote: >> autofrettage> any kind of rower = Ruder*in > > But with the 'female' suffix? Thatʼs almost as bad as 'écriture > inclusive'. Surely 'Ruder**'? The German wikipedia page* about gender neutral language is well over 30 k words long, and there are almost 250 bibliographic references. It lists a number of alternatives, such as (based on Lehrer and Lehrerin, the German words for teacher): + Lehrx + Lehry + Lehrerin + Lehrer/-in + Lehrer/in + LehrerIn + Lehrer(in) + Lehrer:in + Lehrer*in + Lehrer_in + Lehrer_In + Lehrer•in + Lehrkraft + Lehrperson + Lehrende + ... So, by all means, join the party. They will consider all aspects of your suggestion, and being dead serious about it. Yours Rasmus * https://de.wikipedia.org/wiki/Geschlechtergerechte_Sprache p.s. There are even browser plug-ins, removing all of this political correctness, making texts _much_ easier to read.
Re: Org-syntax: Intra-word markup
Someone brought up edge and corner cases, so I simply have to mention the
German gender stars ("Gendersternchen").
In an effort to make German gender neutral, some individuals use '*' in the
midst of some words, e.g. rower.
Ordinary German:
male rower = Ruderer
female rower = Ruderin
Gender neutral German with gender star:
any kind of rower = Ruder*in
Yours
Rasmus
Re: Why is an image width restricted to being between 0 and 200% of the text area
Hi, If org mode won't blow up, kick out the restriction. It is not up to us to decide what users will have use for or not. Besides, if someone specifies an outrageously wide picture by mistake, it's a mistake which is easy to spot and fix. I finish my argument with a small war story. Many years ago my colleagues and I tried to create a computational grid around a ship, for flow simulations. However, the grid generation program refused to follow our instructions, no matter what we tried. We reported this to the company behind the grid generation software, and it turned out they had imposed a 1000 m size limit on grids. It just so happens that many merchant ships are almost 400 m long, and when you extend the computational grid sufficiently up- and downstream, you get a grid well over 1000 m long. Given the magnitude limit for double precision floating point numbers, 1000 m was a ridiculous limit. yours Rasmus
[BUG] org-cite-insert ignores JSON entries with editors only [9.5 (9.5-g0a86ad @ /home/rasmus/.emacs.d/elpa/org-9.5/)]
Hi,
I recently used oc-basic and oc-csl but ran into a slight problem when I tried
to cite
"97 Things Every Programmer Should Know — Collective Wisdom from the Experts",
1st ed.; Henney, K., Ed.; O’Reilly Media, Inc., 2010.
...with the command org-cite-insert. Typing "Henney" produced no suggestions.
After editing the JSON file from Zotero manually, making Henney an author
instead of an editor, everything worked as expected.
As you may guess, the book is a collection of expert tips from many different
programmers, and Kevlin Henney is "just" the editor.
The same happened for some other sources having editors, but no authors.
Yours
Rasmus
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.23,
cairo version 1.16.0)
of 2021-01-18, modified by Debian
Package: Org mode version 9.5 (9.5-g0a86ad @
/home/schoon/.emacs.d/elpa/org-9.5/)
current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-link-shell-confirm-function 'yes-or-no-p
org-num-format-function 'org-num-default-format
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-download-annotate-function 'org-download-annotate-default
org-modules '(ol-bibtex ol-docview ol-eww ol-info org-tempo)
org-plantuml-jar-path "/usr/share/plantuml/plantuml.jar"
org-calc-default-modes '(calc-internal-prec 16 calc-float-format (float 16)
calc-angle-mode
deg calc-prefer-frac nil calc-symbolic-mode nil
calc-date-format
( "-" MM "-" DD " " Www (" " hh ":" mm))
calc-display-working-message t)
org-mode-hook '(org-tempo-setup
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-show-all append local]
5]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-babel-show-result-all
append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-download-file-format-function 'org-download-file-format-default
org-footnote-section nil
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn
ENTRY)"]
org-adapt-indentation t
org-babel-pre-tangle-hook '(save-buffer)
org-file-apps '((auto-mode . emacs) ("\\.mm\\'" . default) ("\\.x?html?\\'" .
system)
("\\.pdf\\'" . "/usr/bin/evince %s"))
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-babel-load-languages '((emacs-lisp . t) (python . t) (gnuplot . t)
(asymptote . t)
(plantuml . t) (shell . t) (dot . t) (ditaa . t))
org-export-backends '(ascii beamer html latex md odt)
org-babel-python-command "python3"
org-agenda-loop-over-headlines-in-active-region nil
org-src-lang-modes '(("ocaml" . tuareg) ("elisp" . emacs-lisp) ("ditaa" .
artist)
("asymptote" . asy) ("dot" . fundamental) ("sqlite" . sql)
("calc" . fundamental) ("C" . c) ("cpp" . c++) ("C++" .
c++)
("screen" . shell-script) ("shell" . sh) ("bash" . sh)
("plantuml" . plantuml))
org-cite-export-processors '((latex biblatex nil nil) (t basic nil nil))
org-occur-hook '(org-first-headline-recenter)
org-ditaa-jar-path "/usr/share/ditaa/ditaa.jar"
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-speed-command-hook '(org-speed-command-activate
org-babel-speed-command-activate)
org-footnote-define-inline t
org-babel-tangle-lang-exts '(("asymptote" . "asy") ("python" . "py")
("emacs-lisp" . "el")
("elisp" . "el"))
org-export-before-parsing-hook '(org-attach-expand-links)
org-confirm-shell-link-function 'yes-or-no-p
org-link-parameters '(("info" :follow org-info-open :export org-info-export
:store
org-info-store-link)
("eww" :follow org-eww-open :store org-eww-store-link)
("docview" :follow org-docview-open :export
org-docview-export :store
org-docview-store-link)
("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
("attachment" :follow org-attach-follow :complete
org-attach-complete-link)
("id" :follow org-id-open) ("file+sys") ("file+emacs")
("shell" :follow org-link--open-shell)
("news" :follow
#[514 "\301\300\302Q\"\207" ["news" browse-url ":"] 6
"\n\n(fn URL ARG)"]
Re: Installation on offline machines
> /.../ the elpa-mirror package helps out for the "niche" of > users who need to deploy the extensions on machines that do > not have access to the internet. I found out about and used elpa-mirror when I worked in Windows Subsystem for Linux (WSL). Its connection with the net was somewhat mysterious to me, and elpa-mirror was the answer. WSL may have improved since then. Yours Rasmus
[BUG] org-toggle-headline inserts "TODO" regardless of local definitions [9.5 (9.5-g0a86ad @ /home/rasmus/.emacs.d/elpa/org-9.5/)]
Dear all, Here comes a minor gripe. If I start with: - #+TODO: foo bar | baz + [X] Apple + [ ] Banana ...and then apply org-toggle-headline (C-c *) on the two items, one after the other, I end up with these headlines: * DONE Apple ** TODO Banana ...instead of these: * baz Apple ** foo Banana Yours Rasmus
Re: "Unknown processor biblatex"
> Note the thread I posted a day or two ago /.../ Thanks I will, and I will also try to remember to search the mail archives the next time around. Yours Rasmus
"Unknown processor biblatex"
Hi all, I have really seen forward to the release of org mode 9.5 with its new and shiny support for citations. The initial frenzy of experimentation has lead to mixed results. Right now I am trying to use the biblatex processor, but I only get "Unknown processor biblatex". How is that even possible, when that should be one of the processors provided by org mode 9.5? Are there more packages, like citeproc.el, on which org-cite depends, and I have to install manually? Is there some mandatory set-up I have failed to notice? I have tried to read https://blog.tecosaur.com/tmio/2021-07-31-citations.html and the manual page for the citations, but I am at my wits' end now. Any pointer would be appreciated. Yours Rasmus
Re: Release 9.5
> Org 9.5 is out, available from GNU ELPA. I bow to the ground in utter and humble gratitude! > Enjoy! I will, that is as certain as taxes and death! Cheers Rasmus
Re: visual-line-mode: virtual-auto-fill-mode better
Hi, Uwe wrote: > I am not entirely convinced by this mode and now came across > virtual-auto-fill-mode that looks to me a much nicer solution. > Any comments? I haven't tried virtual-a-f-m myself, so I cannot say if it is the ultimate solution. However, I have tried visual-fill-column- mode together with visual-line-mode. The tags tended to mess things up, until I started to use these settings: # Local Variables: # eval: (visual-line-mode) # fill-column: 72 # org-tags-column: -69 # eval: (visual-fill-column-mode) # eval: (auto-fill-mode -1) # End: cheers Rasmus
Re: A requires/provides approach to linking source code blocks
Tim wrote: > This could just be me, but recently, I'm becoming very concerned > about the growth of additional features and options in org mode. Count me in. I have been mostly been hanging around in the shadows, but this is serious enough for me to wave a flag on the right side. I would go as far as saying that several suggestions have been so niche, as to be labeled feature bloats. They can be made available as user-added extensions through melpa, but should stay outside org itself. just my ¢2 Rasmus
Re: LaTeX-producing code : how to export results to HTML/ODT
Hi, I simply cannot ignore this opportunity to expose my utter Org Mode ignorance! Emmanuel > ... and how to use it with captions, labels and cross-references. I have tried using the code-splicing functionality with some success; The result from one source code block "foo", can be inserted into another one with <>. If you take away the parentheses, then the source code block "foo" instead of its results will be inserted. Emm.> But I still don't "get" drawers, I thonk. You're not alone. Rasmus
Re: About multilingual documents
Hi, I must confess I haven't followed all the nooks and crannies of this subject, but when I browsed through the latest batch of contributions, I noticed that one simple (=crude) workaround hasn't been mentioned; Indirect buffers. If one uses one indirect buffer per language, it should be possible to select a separate flyspell language for each buffer. Jumping between buffers/windows is perhaps less of a hassle than constantly switching spell checking languages. I suspect the ambitions of the general list member is higher than that, but this workaround could ease the pain for some of us. Cheers Rasmus
Re: Possible small formatting change in manual (section 15.1)
Ian wrote: > When the paragraph first introduces the term “live code > block”, it’s italicized. I think it should stay italicized > for the rest of that paragraph since it’s the introduction > of the term I am not one of the authors of the manual, but my impression, after spending most of my life reading manuals, scientific reports, and a lot of other terminology-rich literature, is that new terms are typographically emphasised once and once only. Cheers Rasmus
Re: "#+STARTUP: hideblocks" has no effect?
Kyle> Are you leaving org-startup-folded at showeverything Yes I do. Kyle> That will prevent org-startup-folded and "#+startup: Kyle> hideblocks" from having an effect: I must admit I was pig ignorant of that. Kyle> For example, try this: Specifying "#+startup: nofold" together with "#+startup: hideblocks", as suggested, worked like a charm! Case closed, and I will try to RTFM the next time. Cheers Rasmus
Re: Including Email Address in the Reply in Mailing-list
> I just noticed that some of us here, when replying, include the email of > the sender of the previous email in the response as part of body of the > email. /.../ > I suggest refraining from doing so, and instead use the name. Good idea! Cheers Rasmus
"#+STARTUP: hideblocks" has no effect?
Hi, I recently read about the #+STARTUP parameter "hideblocks", but it doesn't seem to have any effect in my set-up. All the blocks kept laughing straight in my face. :-( Any ideas about what could have gone wrong? I use Org Mode 9.4.5 with Emacs 26.3, and I also tried closing the file and Emacs before I tried. Cheers Rasmus p.s. Setting org-hide-block-startup with local variables is a solution, but not as nice as doing it with #+STARTUP, I'd say.
Re: Using backticks for the inline code delimeter?
I vote against backticks, since I think we can learn to live with some diversity. Running with the crowd, the latest fashion, would, in the end, leave us with something like Word and Windows, that is, something which is seductively easy to use the first two days, but a pain in the neck the rest of your life. Unfortunately, I have seen these tendencies in Linux, in Emacs -- yes, live-move-visual is now default, which makes Emacs less consistent, but more like Word -- and even in my favourite window manager. Please evaluate the design of Org Mode (and other things) without putting a value on how similar it is to other things. A bicycle would appear more familiar to a car driver if we replaced the handlebar with a steering wheel, but it wouldn't make the bike any better. If someones fingers cannot adjust, let him/her customise a bit. Just my two cents. Rasmus
Re: Using backticks for the inline code delimeter?
> > I would like to submit that org consider adopting backticks as an alternate > > way of denoting inline code. > > Just FYI, this is almost certainly not going to happen. Perhaps as unlikely as Python adopts 'i' instead of 'j' in complex numbers? It looks awful for all but electrical and electronics engineers. Cheers Rasmus
Re: Using backticks for the inline code delimeter?
Hi, George> Aside from any official movement, I would like to add this to my own files - is there a straightforward way to extend the org parser to do this? Quick and Dirty: Bind key '`' to ~ in Emacs? (I guess it is clear I haven't thought about the consequences.) Cheers Rasmus
Re: About exporting
Martin Steffen wrote: > I cannot imagine > that publishers would prescibe ``this is the org-settings and features > you as author must to use to publish with us''. If anyone, then the IEEE. In the late 80s, their instructions to authors included a mindboggling number of allowable DTP-program (and other) file formats, and an equally mindboggling number of physical storage alternatives. ...but I acknowledge that was over 30 years ago. Cheers Rasmus
Re: About exporting
Hi, Just a remark about what Martin Steffen wrote: > There is one case where I do NOT use org for such documents (though I > use org basically most things I do), and that is > > collaborative editing, > > /.../ one can easily > mess it up (typically for novices, who start changing layout or > typesetting, injecting manual spacing etc). > /.../ > That's why I have not dared to write challenging (latex) documents with > org collaboratively (complex documents alone, yes, simple documents > jointly, but not all) Not even the most streamlined DTP-wysiwyg-program is safe from this. Far from. I even doubt typewritten documents can be written colla- boratively, without someone messing things up. There should be something like pilot licences for using certain computer tools, not to speak about programming, but let's not sink into squabbles about that... cheers Rasmus
Re: About exporting
Hi Ypo and the rest of you all, > After some years of using orgmode, and exporting using its defaults, I would > like to take a quality leap and find a way of exporting for life. My options: > LaTeX, ODT, HTML. /.../ > How do you think I should spend some hundreds (or thousands) of hours to > achieve maestry exporting my documents? I have some odd thoughts about this. About 30 years ago I worked for a start-up company. As a young engineer, freshly hooked on LaTeX, I tried to convince my colleagues we should produce the users' manuals for our product with LaTeX. Since persuasive speech is not one of my strengths, they opted for Word 5. For various reasons I stayed for only a few years. Recently I visited them, and heard that the users' manuals had been ported hither and thither between various wysiwyg DTP programs. They are now back in Word, and my former colleagues didn't even remember the documents had started their journey there! If they only had listened to me in the beginning! The moral seems to be that whatever time and effort you plow into learning LaTeX, will not be wasted. Chances are that LaTeX will be there in thirty years' time, working roughly the same as now. Roughly. At a fine grain level, LaTeX -- not to speak about Org Mode -- is a moving target. How on earth can you hope for attaining mastery at exporting documents? Many individuals are continuously refining these tools, so the mere mortals among us will always fight a losing battle keeping up. Late adoption is a great trick for making life a bit easier. Postpone teaching yourself the latest tricks, until other friendly internet citizens have had time to write streamlined explanations ;-) Last but not least, think like Bruce Lee: “You must be shapeless, formless, like water. When you pour water in a cup, it becomes the cup. When you pour water in a bottle, it becomes the bottle. When you pour water in a teapot, it becomes the teapot. Water can drip and it can crash. Become like water my friend.”* So, teach yourself whatever you need now (where "now" includes a foreseeable future). Cheers Rasmus * LaTeX = ninjutsu, ODT = boxing, HTML = kick in the groin?
SymPy equations + displayed equation + label = difficult?
Hi all,
I have tried to use SymPy in Org Mode code blocks, export LaTeX
expressions to displayed equations, and refer to those with
labels. My current solution is ugly, which has left me with a
strong feeling that there must be a better way.
Sensitive Org Mode users are warned. Here comes a brief
description of my current solution.
* The equation is defined inside a SymPy block, e.g.:
a, R, L = symbols('\\alpha R L')
equ = Eq(R, L * sin(a))
* The LaTeX representation for equ, and the rest of the LaTeX
code needed for producing a displayed equation, with a label,
are generated with the Python function expequ:
#+BEGIN_SRC python :session :results none :exports none
def expequ(expr, label):
# will write out code for export of SymPy equation
expression = latex(expr, mode="plain")
print("""
\\begin{equation}
\\label{%(label)s}
%(expr)s
\\end{equation}""" % {'expr': expression, 'label': label})
#+END_SRC
* At the place where I want to display equ, I call expequ like
this:
#+HEADER: :results output latex overwrite :exports results
#+BEGIN_SRC python :session
expequ(equ2,"equ:labeltest")
#+END_SRC
* ...which yields:
#+RESULTS:
#+BEGIN_EXPORT latex
\begin{equation}
\label{equ:labeltest}
R = L \sin{\left(\alpha \right)}
\end{equation}
#+END_EXPORT
How many painfully obvious solutions have I missed?
Yours
Rasmus
