Dear Org Mode Friends,
I’m having some trouble getting the shell I want to run on remote hosts in
session ob-shell blocks - it seems that no matter what shell I specify, session
blocks will always run /bin/sh. I’m not sure if this is an org or tramp
configuration issue on my end, or a bug in
Steps to reproduce the bug:
1. download orgmode 9.4.6 from https://orgmode.org/org-9.4.6.tar.gz and
extract to home folder
2. start clean emacs instance with 'emacs -Q'
3. evaluate (add-to-list 'load-path "~/org-9.4.6/lisp")
Steps to reproduce the bug:
1. download orgmode 9.4.6 from https://orgmode.org/org-9.4.6.tar.gz and
extract to home folder
2. start clean emacs instance with 'emacs -Q'
3. evaluate (add-to-list 'load-path "~/org-9.4.6/lisp")
Uwe Brauer writes:
> In my experience the best I found was
>
> (defun my-turn-on-longlines-in-auctex ()
> "Turn on all three modes which support the display of long-lines."
> (interactive)
> (adaptive-wrap-prefix-mode 'toggle)
> (visual-line-mode 'toggle)
> (visual-fill-column-mode
On Fri, Jun 25, 2021 at 06:54:25AM +1000, Tim Cross wrote:
[...]
> My view is that if org-mode is stealing the calendar bindings by default
> i.e. user has not enabled some specific option/configuration to do this,
> then this is a bug [...]
AFAIU, Stephen just gave his green light to Stephen's
Stephen Berman writes:
> On Thu, 24 Jun 2021 14:09:46 +0200 to...@tuxteam.de wrote:
>
>> On Thu, Jun 24, 2021 at 12:13:40PM +0200, Stephen Berman wrote:
>>> On Wed, 23 Jun 2021 18:16:52 +0200 to...@tuxteam.de wrote:
>>>
>>> > On Wed, Jun 23, 2021 at 05:28:36PM +0200, to...@tuxteam.de wrote:
My minimal loadup doesn't exhibit the problem. So, tracing the function
"org-agenda-clock-in" that my =C-x TAB= is bound to, I see this.
On the broken one I see the following:
#+begin_src lisp
=1 ->
(org-agenda-clock-in nil)
The convenience of html output is the easiness by which one can zoom
in and out. Doing that in printed output is difficult because you need
typefaces with different sizes.
I use the latex for mathematical typesetting, with the other things I
wholeheartedly follow your drift. There is still so
On 6/24/21 11:43 AM, Christopher Dimech wrote:
I only proposed colour highlighing for mathematical snippets. Nothing else.
Or making org able to export to html even when one is using LaTeX blocks.
In that sense, it would act in ways similar to texinfo, using a single
source file to produce
Hi John!
There is no „return“ in Lisp languages. The return value of (list 1 2 3) is (1
2 3). Clojure is a Lisp language similar to Elisp. So
#+begin_src clojure :results code
(list 1 2 (+ 1 2))
#+end_src
should work for Clojure as it does für Elisp.
Johannes
Am 24.06.2021 um 18:28 schrieb
I only proposed colour highlighing for mathematical snippets. Nothing else.
Or making org able to export to html even when one is using LaTeX blocks.
In that sense, it would act in ways similar to texinfo, using a single
source file to produce output in a number of formats, both online and
On Thu, Jun 24, 2021 at 05:04:02PM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Stephen Berman writes:
>
> > Yeah, the next time Org is merged to the Emacs master branch, forcing me
> > to first stash and then reapply my patch locally, I'll ask if anyone
> > objects to the patch being committed
On Thursday, 24 Jun 2021 at 19:25, Christopher Dimech wrote:
> I conclude that org-mode cauld do with some improvements. If org-mode
> was designed to allow LaTeX fragments without the need of any special
> marking, it should allow latex syntex highlighting without the need of
> any special
Does not say what ARG is !
Could be much better to do "M-x org-latex-preview" to toggle on-off.
Sent: Friday, June 25, 2021 at 4:06 AM
From: "Rodrigo Morales"
To: "Christopher Dimech"
Cc: "Help Emacs Orgmode"
Subject: Re: Latex preview for whole buffer with on-off keybinding
I conclude that org-mode cauld do with some improvements. If org-mode was designed to allow
LaTeX fragments without the need of any special marking, it should allow latex syntex highlighting
without the need of any special markings.
Sent: Friday, June 25, 2021 at 4:28 AM
From: "Rodrigo
On Thursday, 24 Jun 2021 at 10:45, Rob Sargent wrote:
> I am using org version 9.1.9 and libre office version 6.4.7.2
Confirmed with very recent version, as shown in signature.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-571-gc591be
: Latest paper written in org:
It appears to me that explicitly setting list order number is not
honoured by the odt export mechanism. The following works on latex
(list numbering starts at 7) but not on odt (list numbering starts at
one though the [@7] is stripped from the output (as expect)):
1. [@7](/facilities/)
There are two ways with which you can get LaTeX syntax highlighting when
editing LaTeX in org-mode buffers.
* No. 1: LaTeX code blocks
You can have LaTeX code blocks within your document with the following
header arguments and thus have syntax highlighting and make the content
of those code
That probably means the clojure block is returning nil as the value. I
don't know what it means to return something in clojure, but here is what
you have to do with Python, for example.
#+BEGIN_SRC python :results value code
[1, 2, 3]
#+END_SRC
#+RESULTS:
#+begin_src python
None
#+end_src
You
Accomplishing this is explained in the docstring of org-latex-preview:
> org-latex-preview is an interactive compiled Lisp function in
> ‘org.el’.
>
> (org-latex-preview ARG)
>
> ...
>
> With a ‘C-u’ prefix argument ARG, clear images for all fragments
> in the current section.
>
> With a ‘C-u
Org-mode allows latex-preview. But this applies to each latex
expression independently. Is there a way to have a keybinding
that would turn latex-preview "on" or "off" for the whole buffer?
This applies only to snippets
C-c C-x C-l (org-latex-preview)
Hello,
Stephen Berman writes:
> Yeah, the next time Org is merged to the Emacs master branch, forcing me
> to first stash and then reapply my patch locally, I'll ask if anyone
> objects to the patch being committed to master.
Sure, go ahead.
Regards,
--
Nicolas Goaziou
What about :results code
The default is a elisp code block so you get syntax coloring
That works fore lisp:
#+begin_src elisp :results code
(list 1 2 (+ 1 2))
#+end_src
#+RESULTS:
#+begin_src elisp
(1 2 3)
#+end_src
But with Clojure I get
#+begin_src clojure :results code
(list
On Thu, 24 Jun 2021 14:09:46 +0200 to...@tuxteam.de wrote:
> On Thu, Jun 24, 2021 at 12:13:40PM +0200, Stephen Berman wrote:
>> On Wed, 23 Jun 2021 18:16:52 +0200 to...@tuxteam.de wrote:
>>
>> > On Wed, Jun 23, 2021 at 05:28:36PM +0200, to...@tuxteam.de wrote:
>> >
>> > [calendar
On Thu, Jun 24, 2021 at 12:13:40PM +0200, Stephen Berman wrote:
> On Wed, 23 Jun 2021 18:16:52 +0200 to...@tuxteam.de wrote:
>
> > On Wed, Jun 23, 2021 at 05:28:36PM +0200, to...@tuxteam.de wrote:
> >
> > [calendar insert-diary-entry doing funny things]
> >
> > OK, I solved it by setting
On Thursday, 24 Jun 2021 at 10:46, Johannes Brauer wrote:
> #+begin_src clojure :results verbatim :wrap src clojure
> (list 1 2 (+ 1 2))
> #+end_src
For completeness, another option is ":results verbatim drawer" without
:wrap.
--
: Eric S Fraga via Emacs 28.0.50, Org
Hi Rodrigo!
Thanks a lot for the detailed information. In the meantime I’ve studied the
org-mode manual a bit more closely (perhaps, I should have done that before
asking my question …) and found the following interesting possibilitiy:
#+begin_src clojure :results verbatim :wrap src clojure
On Wed, 23 Jun 2021 18:16:52 +0200 to...@tuxteam.de wrote:
> On Wed, Jun 23, 2021 at 05:28:36PM +0200, to...@tuxteam.de wrote:
>
> [calendar insert-diary-entry doing funny things]
>
> OK, I solved it by setting `org-calendar-insert-diary-entry-key' to
> [106], which is a ?j. It was set to ?i,
Hi Jeremie,
> Jeremie Juste writes:
> Hello,
> With the following patch the link to graphics output is finally
> back on with R source code. Note that on top of the "graphics"
> parameter the "file" parameter have to be used for the org-link to
> work out of the box. I
Sébastien Miquel,
> If I try your original examples with `emacs -q' I do not get extra
> whitespace in the org src buffer. Those two spaces in the original org
> buffer -- that are due to `org-edit-src-content-indentation' -- are
> removed in the org src buffer. If you do not find it to be the
Hello,
** Christopher Dimech [2021-06-24 06:50:50 +0200]:
> Am using org-mode with latex commands but need to have the page as b6paper.
Try 'geometry' package,
(untested)
#+LATEX_HEADER: \usepackage[b6paper]{geometry}
---
WBR, Vladimir Lomov
--
Honesty pays, but it doesn't seem to pay
Hi Ihor,
Ihor Radchenko writes:
> What about duplicates? If you insert all the feeds from the last few
> months and then update the same headline weeks later, there will overlap
> between elfeed entries.
When I update a headline, all previous feeds are removed, so there is no
possibility of
On Wednesday, 23 Jun 2021 at 15:42, Gennady Uraltsev wrote:
> In Org Mode, headings cannot "terminate" i.e. only a new section can
> stop a previous one.
True.
What I do for cases where I want "separation" for visibility etc. is use
headings at the same level but tell the exporter to ignore the
33 matches
Mail list logo
