Hi Ihor,
Ihor Radchenko writes:
> Org mode fontification routines do not support multiple different
> variants of major mode in src blocks.
> We also cannot handle major modes prompting user when they are
> activated.
>
In case you missed it, the workaround that solved
the OP problem is:
(s
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>>> #+begin_src scheme :scheme chez
>>>> (+ 3 4)
>>>> #+end_src
>>>>
>>>> and also with ':scheme racket'.
>>>>
>>>> Unfortunately, it does
Hi Rodrigo,
Rodrigo Morales writes:
> I saved the contents of the code block below to the file =/tmp/a.org=.
>
>
> I wish those ^M were not shown in the sh code blocks in the Org Mode
> buffer. Does anyone know how to accomplish this behavior?
>
Your result is mixing different "end-of-line" c
Roi Martin writes:
> Bruno Barbier writes:
>
>> My patch fixes a real bug though. Are you sure org is using the correct
>> scheme implementation when doing "C-c C-c" ?
> I think it works fine if you set the `org-babel-load-languages' variable
> in
Roi Martin writes:
> I tried the current main branch (commit da0f6eff75cd ("ox-texinfo: Fix
> edge case with - Variable: nil:: definition") with and without the
> patch. Unless I'm doing something wrong, exporting the document to HTML
> with "C-c C-e h H" asks for the Scheme implementation
#+RESULTS:
: Welcome to Racket v8.14 [cs].\n
(setq-default geiser-chez-binary "chezscheme")
#+begin_src scheme :scheme chez
(scheme-version)
#+end_src
#+RESULTS:
: Chez Scheme Version 10.0.0
Could you try it?
Bruno
>From dbb3068bd3e22ee8d38c99c69061b26d3
Hi Roi,
Roi Martin writes:
> If I understand correctly, I can set a default Scheme implementation
> with the `geiser-scheme-implementation' variable. However, I would like
> to specify an implementation per block without having to answer the
> prompt every time.
>
> Is it possible?
According
Hi Sébastien,
Sébastien Gendre writes:
[...]
> I cannot found a way to define "very-strawbery" value in an Org-mode
> buffer and having it used while I manually export the Org-mode buffer.
>
> I tried with "#+very-strawbery: test123" and "#+OPTIONS: very-strawbery:
> test123", without success.
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
[...]
>>> Ideally, we should have no hard-coded color names.
>>
[...]
> If you have no ideas about faces to inherit from, better keep hard-coded
> colors.
>
> (Also, this is not too critical; just
Hi Angelo,
Angelo Graziosi writes:
> With the last Emacs master build (20240731_183641) I get a lot of
> warnings like this:
>
>
> Warning (emacs): Cannot fontify source block (htmlize.el >= 1.34 required)
>
>
> when I export an old ORG document in HTML (C-c C-e h h).
>
> Until some time ago,
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>>> I added a function 'org-pending-unlock-NOW!' which unlock the region
>>>> immediately. The uppercase "NOW!" emphasizes that it's not the
>>>> "safe"
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> I added a function 'org-pending-unlock-NOW!' which unlock the region
>> immediately. The uppercase "NOW!" emphasizes that it's not the
>> "safe" way to unlock a regio
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> About how much to decorate, it depends on the user, I guess. For
>> example, when org-pending is used for org babel, it should be obvious
>> that one has to click on "#+RESULTS:".
>>
>&
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
> I have one suggestion though. You now do
>
> Use the function ON-OUTCOME to update the region with the outcome; if it
> is nil, set it to the function `org-pending-on-outcome-replace'.
>
> Howe
Hi,
Uwe Brauer writes:
> However if in table1 there is an empty entry in the relevant column,
> remote copies it as 0
>
> #+begin_src
>
> #+NAME: table2
> | Name | Ex1 | Ex2 | Ex2 | Ex4 | Ex5 | ResSh1 |
> |+-+-+-+-+-+|
> | Smith | | 3 | 4 | 6 |
Hi Sébastien,
Sébastien Gendre writes:
> TL;DR: How can I use the Org-mode macros as LaTeX macros inside an
>export LaTeX bloc ?
>
It looks like macros are not expanded in latex export blocks, indeed.
You may define your own filter to ask Org to expand them.
With the 2 functions be
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>>> ;;(org-pending-send-update my-rlock (list :progress "Not ready
>>>> yet."))
>>>> ;;(org-pending-send-update my-rlock (list :progress "Coming
>>>> soon
Ihor Radchenko writes:
> Bruno Barbier writes:
>
> I am attaching some minor edits I'd like to propose on top of your
> latest branch.
I've applied your patch. Thanks.
> Also, some more questions.
>
>> ;;(setq my-rlock
>> ;;
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> I've pushed the modification to my branch.
>
> Thanks! Let's work further on the top comment.
>
>> ;; To lock a region, you need to do something like this:
>
> I think "something lik
Thanks for the review Ihor!
>> Thanks. I've improved the documentation of `org-pending' to mention
>> that one may want to customize the following fields of a reglock:
>> before-kill-function, user-cancel-function and
>> insert-details-function. And, also, I added that one can attach
>> custom
Hi Ihor,
Thanks for the review.
I've pushed a new version, hoping to decrease the number of dislikes
;-)
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>> I have a further request on interaction with penreg objects.
>>> I feel that it is not ideal that ov
Rudolf Adamkovič writes:
>
> +1 for the full name.
>
> Searching 'M-x' for 'region' gives 229 results on my Emacs, so there is
> a precedent. In fact, when I first read the name 'reglock', I took
> 'reg' for *not* a region, but register or registry, precisely because
> Emacs consistently spell
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> I've pushed an update that should address most of your comments.
>
> Thanks!
>
>> I've found a better name: I'm now calling it a "lock". So I renamed
>> "PENREG" into "
Hi Ihor,
Thanks for your review and detailed explanations.
I've pushed an update that should address most of your comments.
Let me answer point by point below.
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>> I feel that org-pending-penreg (org-pending-) is
>>
Ihor Radchenko writes:
Thanks for your review Ihor!
> Bruno Barbier writes:
>
>> I rewrote the API, rename many things, moved the code around and
>> sorted everything into heading/subheading sections. This is hopefully
>> less confusing and a lot simpler; and the
Ihor Radchenko writes:
> Bruno Barbier writes:
>> Would "lisp/org-pending.el" be OK ? Or do you see a better place/name ?
>
> org-pending sounds fine. Maybe org-pending-text to be more explicit.
I've picked: "org-pending"; it's shorter and ca
Ihor Radchenko writes:
>
> Thanks for reporting!
> Fixed, on bugfix and main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8b73c8b98
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=712ef988c
It now works.
Thanks Ihor!
> --
> Ihor Radchenko // yantar92
Hi,
Org removes all overlays when calling org-babel-execute-subtree.
Here is a way to reproduce:
#+begin_src elisp
(with-temp-buffer
(let (ovl
(statuses nil)
(live-p (lambda (xo) (or (and (overlay-buffer xo) "alive")
"dead"
(insert
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>> If you've gotten this far you probably know more
>>> about the Haskell Babel situation than you ever wanted to, but maybe you
>>> can sniff out where this hardwire is happening.
>>
>
Hi Antonio,
Antonio Romano writes:
[...]
> The :todo-keyword contains data about face and properties which are
> only relevant for viewing the document in the buffer and not for the
> .org file content itself. How can I read its text without any property
> info attached to it?
You could remov
Hi Sébastien,
Sébastien Gendre writes:
> Hello,
>
> How can I access to an in-buffer setting value, from Elisp code ?
>
IIUC, they are called "Buffer-Local Variables".
Using 'buffer-local-value' should give you the value of a variable in a
buffer.
See the manual for more:
(info "(elis
Hi Laurence,
Laurence von Bottorff writes:
> I'm on Debian 12 and I just started using Haskell's ghcup tools, leaving
> the stack tools behind, as advised these days. ghcup puts executables for
> Haskell such as ghc, ghci (REPL), cabal, etc. in its ~/.ghcup/bin
> directory. Next, to stop using
Hi Ihor,
Ihor Radchenko writes:
> Thanks!
> I have some minor concerns about implementation, but you clearly
> demonstrated the things can be working in general.
Thanks!
> While reading the library header and `org-pending' docstring (btw, it
> should probably be a separate library, not a par
William Denton writes:
> On Thursday, February 29th, 2024 at 04:25, Bruno Barbier
> wrote:
>
[...]
> I checked:
>
> | Its value is (latex)
> | Original value was nil
>
> I didn't have a chance to dig back into this but now I see other people are
> repor
Hi,
Bruno Barbier writes:
> Ihor Radchenko writes:
>
>> Bruno Barbier writes:
>>
>>>> Overlays are not transferred when a new indirect buffer is created (for
>>>> example, by org-capture, or by user). So, it will be (1) impossible to
>>>&
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>> Overlays are not transferred when a new indirect buffer is created (for
>>> example, by org-capture, or by user). So, it will be (1) impossible to
>>> see pending overlays in indirect buffers; (2) user edits
Hi Ihor,
Ihor Radchenko writes:
[...]
>> I've tried to fully describe the feature in the new section "Pending
>> contents", in the file `lisp/org-macs.el'.
>
> I have one general concern about the implementation.
>
> Overlays are not transferred when a new indirect buffer is created (for
> exam
Bruno Barbier writes:
> Hi William,
>
> William Denton writes:
>
>> I rebuilt Org and Emacs from the development trees and something is wrong,
>> because some Org files I use regularly have become incredibly slow to use.
>> I rarely use the profiler and don&
Hi William,
William Denton writes:
> I rebuilt Org and Emacs from the development trees and something is wrong,
> because some Org files I use regularly have become incredibly slow to use. I
> rarely use the profiler and don't know what to make of what it says, but I
> opened a file and ra
Hi Matt,
Matt writes:
> On Sat, 24 Feb 2024 17:42:54 +0100 Bruno Barbier
>
> > I'll publish a branch soon; it will be a major rewrite of my current
> > proposal. It should be less confusing and, I hope, address some of your
> > comments.
> >
&
Hi,
Bruno Barbier writes:
> Hi Matt,
[...]
>> Since this thread is dedicated to blocking, let me share my thoughts on that
>> subject.
>
> I guess I should start a new thread then :)
I finally got a new version. I've renamed the proposed feature "pending
co
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>> May you please clarify if adding the new code block parameter that
>>> defines custom execute function is something you want to add to Org mode
>>> or just a helper code to demo you main patch?
>>
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> Note that only the first 5 patchs are real patchs. The remaining things
>> are just a demo how it could be used. The current async (ob-comint)
>> depends on writing UUIDs in org files, and, that's why I could
Hi Rudy,
Note that I am not an org maintainer; just trying to help :-)
Rudi C writes:
>> Why is `:eval never` not as good ? You don't have to write it on each
>> code block; you may set it globally, per file, per headline, etc.
>
> The main reason is that I also use source blocks for babel b
Hi Rudi,
Rudi C writes:
> After upgrading to emacs 29.2 and org 9.7, my example blocks are no longer
> syntax highlighted in emacs. They used to be syntax highlighted when I
> specified the block's language. Any ideas?
>
> I use Doom, so it might have been a third-party feature.
>
> I know org
Hi Ihor,
Ihor Radchenko writes:
>
> Thanks for the code!
> It is a lot more that I expected.
Note that only the first 5 patchs are real patchs. The remaining things
are just a demo how it could be used. The current async (ob-comint)
depends on writing UUIDs in org files, and, that's why I c
Hi Jack,
Jack Kamm writes:
> Bruno Barbier writes:
>
>> I'm not using it with official org backends (yet). I'm using it with
>> several custom backends that I'm working on. One of the backend
>> delegate the block executions to emacs subprocess
Hi Matt,
Thanks for your answer.
Matt writes:
> ...
> If I understand correctly, there are several independent topics the code
> addresses:
>
> | topic| manner addressed |
> |--+|
> | ex
Hi Matt, Jack, Ihor,
Sorry for the late reply. Cleaning the code took me longer than
expected.
Jack Kamm writes:
> Bruno Barbier writes:
>
>> FWIW, I've been trying to use asynchronous blocks for everything, not
>> only the source blocks that are based on the comint
Ihor Radchenko writes:
> Jack Kamm writes:
>
>> On executing any python session block I am getting the following error
>> which I think is caused by the above:
>>
>> Debugger entered--Lisp error: (void-variable buffer-name)
>
> That's a mystery.
It looks like 'when-let*' doesn't accept symb
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> While the execution is pending, I'm using the same technique that Org is
>> using when a source block is being edited: the result is left untouched,
>> but below an overlay. The overlay is used to know where t
Hi Ihor, Jack,
Ihor Radchenko writes:
> Jack Kamm writes:
>
>> I agree that it would be good to redesign it, but am not sure where to
>> start.
>
> For example,
>
> 1. Change `org-babel-comint-async-register' to return UUID and to store
>PARAMS as passed by the backend (current approach
Hi Ihor,
Ihor Radchenko writes:
>
> This is most likely something about my current system setup - I can
> reproduce with other Org mode and Emacs versions. But I have no clue
> what is the cause.
I'm getting the same as you with your MWE.
The tag, used by ob-comint async, is:
"/tmp/ba
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> FWIW, M-x shell differs from what a plain terminal is doing (xterm, in
>> my case), but, I do prefer 'M-x shell' behavior: it allows me to copy
>> multiple lines, getting the same results as when I type them
Hi Max,
Max Nikulin writes:
> On 17/11/2023 22:47, Bruno Barbier wrote:
>> FWIW, M-x shell differs from what a plain terminal is doing (xterm, in
>> my case), but, I do prefer 'M-x shell' behavior: it allows me to copy
>> multiple lines, getting the same resul
Matt writes:
> On Sat, 18 Nov 2023 09:54:46 +0100 Bruno Barbier
>
> It's still not clear to me if this is "what Emacs does". However, that's the
> best I could come up with.
>
> Evaluating the following
>
> #+name: /tmp/test.sh
> #
Matt writes:
> On Sat, 18 Nov 2023 09:29:56 +0100 Bruno Barbier
>
> > IIUC, what Max is saying is that you should not concentrate on
> > *that specific command* because that command doesn't do what you think
> > it does.
>
> Cool, it sounds like
Max Nikulin writes:
> On 25/10/2023 18:17, alain.coch...@unistra.fr wrote:
>> By contrast, it works with this one:
>>
>> #+begin_src bash :results output
>> sshcoch...@fruc.u-strasbg.fr "echo foo>foo_file" ; echo "bar"
>> #+end_src
>
> What about
>
> #+begin_src bash :results ou
Matt writes:
> On Sat, 18 Nov 2023 04:11:03 +0100 Max Nikulin wrote ---
>
> > > bash -c bash /tmp/two-lines.sh
> >
> > From my point of view it was a plain mistake in attempts to simulate
> > the issue outside of Emacs. There is no point to concentrate on this
> > command.
Hi Matt,
Thanks this summary and for working on this!
Just a few comments/corrections about some specific points, hoping it
might help.
Matt writes:
> On Fri, 17 Nov 2023 10:20:28 +0100 Ihor Radchenko wrote ---
>
> > This has nothing to do with Emacs comint and this is also not a b
Hi Matt, Ihor, Alain,
Ihor Radchenko writes:
> alain.coch...@unistra.fr writes:
>
>> At the most basic user level (i.e., non lisp aware), why is it not
>> necessarily a bug if "something" does the expected in an X terminal
>> but not in an emacs terminal? I think Matt and I (and others) are o
Hi Uwe,
Uwe Brauer writes:
> Hi all
>
> Please look at
>
> | | Price |
> |---+|
> | / | 10.98 |
> | | 11.90 |
> | | 19.98 |
> | | 13.79 |
> | | 29.97 |
> | | 18.98 |
> | | 13.79 |
> | | 11.90 |
> | | 24.28 |
> |---+|
> | | 155.57 |
> #+TBLFM: @11$
Hi,
alain.coch...@unistra.fr writes:
> Ihor Radchenko writes on Thu 26 Oct 2023 13:44:
>
> > I can now reproduce the problem locally.
> >
> > It boils down to
> >
> > (setq exit-status
> > (process-file shell-file-name input-file
> >(if error-file
> >
Uwe Brauer writes:
>> Uwe Brauer writes:
>
>
>> I just tested your example. It works for me, exporting to HTML. I'm
>> using org version 9.7-pre.
>
>> What is the error ?
>
> Well since I did not set a list, org mode complained about it. Not in
> your case? I exported to LaTeX but it should mak
Uwe Brauer writes:
>>>> "BB" == Bruno Barbier writes:
>
>> Did you try org-export-select-tags ?
>
>> (I didn't but, from its documentation, it might be what you're looking
>> for).
> ,
> |
> | Yes I tr
Hi,
Uwe Brauer writes:
>
> So it would be very handy to configure the exporter for that file
> locally that he only exports sections that have a export tag
>
> Is this possible?
Did you try org-export-select-tags ?
(I didn't but, from its documentation, it might be what you're looking
for).
Hi Uwe,
Uwe Brauer writes:
> Here is an example where the org-lookup-first method seems to fail
> #+TBLFM: $3='(org-lookup-first $2 '(remote(Table1A, @I$1..@II$1))
> '(remote(Table1A, @I$7..@II$7)))::$4='(org-lookup-first $2 '(remote(Table2A,
> @I$1..@II$1)) '(remote(Table2A, @I$7..@II$7))):
Hi Ye, Ihor, Max,
The change seems to come from this commit:
commit d7a55bbd537314d2776b082bd92a1a08b3edc84e
Date: Wed Sep 28 12:07:14 2022 +0800
org-latex-export-to-latex: Do not suppress major modes in babel
It replaces 'write-file' with 'write-region', but, according to the
docum
Uwe Brauer writes:
>>>> "UB" == Uwe Brauer writes:
>
>>>> "BB" == Bruno Barbier writes:
>>> Hi Uwe,
>
>>> Uwe Brauer writes:
>>>> so the question is what is equivalent of VLOOKUP in org.
>
>>>
Uwe Brauer writes:
>>>> "BB" == Bruno Barbier writes:
>> Did you check these lookup functions in the Org manual?
>>(info "(org) Lookup functions")
>
>
> Yes of course, but I am unable to obtain the same result as I do using
> the re
Hi Uwe,
Uwe Brauer writes:
> so the question is what is equivalent of VLOOKUP in org.
Did you check these lookup functions in the Org manual?
(info "(org) Lookup functions")
Bruno.
>
> I came up with the remote command that results in a similar result, (I did
> not want to use third
Hello Paul,
Paul Stansell writes:
> It seems to be on a todo list already as the following exists:
> - https://list.orgmode.org/877cqwbpa2@runbox.com
Right. Thanks for the link!
You just need to wait a little :-)
You should probably send an email to the emacs bug:
bug#66213: named
Paul Stansell writes:
>
> By the way, there is a small error in your example as your $3 should be $4.
Oops. Sorry. Thanks for reporting it.
Bruno
Hi Paul,
Paul Stansell writes:
> Hello,
>
> On this page https://orgmode.org/manual/Advanced-features.html
> it says
> - '!' :: The fields in this line define names for the columns, so that
> you may refer to a column as '$Tot' instead of '$6'.
> ...
> |---+++|
> | ! | c1 | c2 |
Hi Chris,
Chris Keschnat writes:
>
> | 19:55:00 |
> | 00:00:40 |
> | 00:00:40 |
> #+TBLFM: $1=if(@# <= 1, 19:55, 40:01);T
>
> What would be the correct way to do this?
>
It seems that org tries to convert times back and forth when evaluating
formulas; but, in your case, it cannot convert them
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> From 86a5443948fc84a6a412ccf49d0c537608f465a7 Mon Sep 17 00:00:00 2001
>> From: Bruno BARBIER
>> Date: Fri, 18 Nov 2022 20:14:20 +0100
>> Subject: [PATCH 1/7] ob-haskell: Add tests for GHCi
>> ...
>
&
Hi Ihor,
Sorry for the delay, thanks again for the ping.
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>>>> + (when (bufferp "*haskell*") (error "Conflicting buffer
>>>> '*haskell*', rename it or kill it."))
>
Hi Ihor,
Ihor Radchenko writes:
> A few months have passed since the last activity in this thread.
> Bruno, may I know if you are still interested to work on the patch?
Thanks for the reminder. I'm definitely interested to closing that
thread.
I'll review my last changes and send my updated
Hi,
Uwe Brauer writes:
> A solution is to put 0 in colum 4, but for some reasons which are a
> complicated to explain, I want to avoid that.
>
> | Name | Exam1 | Exam2 | Exercises | Ex1_Ex2 | Total |
> |---+---+---+---+-+---|
> | Smith | 5.9 | 7.90 |
Hi Ihor,
Thanks for the review.
Ihor Radchenko writes:
> Bruno Barbier writes:
> I can see that you limited the tests scope to :session blocks.
> Would it be possible to extend the existing tests to :compile yes case?
> From a glance, it does not look like you need to
Jeff Trull writes:
> While investigating an error executing a table formula I discovered that
> cells containing '$' cause column references to be executed even when no
> attempt is made to evaluate cell contents as code. Here's a simple example:
>
Confirmed.
org tries first to resolve all r
Ruijie Yu writes:
> Minor remarks below regarding the patchset.
>
> Bruno Barbier writes:
>
>> +;; Copyright (c) 2023 Free Software Foundation, Inc.
>
> lisp/org.el has only a single space, so probably single space here as well.
Done.
>> +
>> +;; Auth
Hi Ihor,
Sorry for the delay.
Bruno Barbier writes:
> Ihor Radchenko writes:
>
>> Bruno Barbier writes:
>>
>>> Note that I've changed the tests about errors; I'm now expecting
>>> ob-haskell to raise errors. I'm not sure what we shou
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> Note that I've changed the tests about errors; I'm now expecting
>> ob-haskell to raise errors. I'm not sure what we should expect to be
>> consistent with other org babel backends.
>
> Errors a
[1]:https://downloads.haskell.org/ghc/latest/docs/users_guide/ghci.html#the-it-variable
>From 46e8fa78574908a15fe6eb82a2cca5d2f537c78e Mon Sep 17 00:00:00 2001
From: Bruno BARBIER
Date: Fri, 18 Nov 2022 20:14:20 +0100
Subject: [PATCH 1/7] ob-haskell: Add tests for GHCi
testing/lisp/test-ob-hask
Hi Ihor,
Ihor Radchenko writes:
> From a first look, random failures appear to be related to session
> initialization.
My function 'test-ob-haskell-ghci' should protect against that; it
ensures the "*haskell*" buffer is always new. From what I understand,
this is an input buffering problem:
Hi Ihor,
>> Bruno Barbier writes:
>>
>>> Sorry, I'm still working on adding a 'test-ob-haskell.el', when I have
>>> some spare time, but I'm unable so far to find tests that I can't
>>> reliably break.
FTR: I've opened a
s-version | 29.0.60 |
| org-version | main@4cad6c8ea (Mar 16 2023) |
| haskell-mode | master@20d4e23 (Mar 4 2023) |
| ghci |9.0.2 |
Bruno
>From c085fac2fcb429f7e643df8e4fff3a4ae1665d07 Mon Sep 17 00:00:00 2001
From: Bruno BARBIER
Da
Hi Ihor,
Ihor Radchenko writes:
> Bruno Barbier writes:
>
>> Sorry, I'm still working on adding a 'test-ob-haskell.el', when I have
>> some spare time, but I'm unable so far to find tests that I can't
>> reliably break.
>
> May I know i
Hi Zelphir,
Zelphir Kaltstahl writes:
> On 3/7/23 20:52, Bruno Barbier wrote:
> Also thanks for the idea with sessions + separate import source block. I
> thought
> that should work, but apparently that also has the same error, when running
> for
> the first time:
>
Hi Chris,
chris writes:
> On Thursday, 2 March 2023 20:00:14 CET Bruno Barbier wrote:
>> The behavior looks the same using only text-mode (without using org).
>> You should probably report this as an Emacs bug (see M-x
>> report-emacs-bug).
>
> What command for
Zelphir Kaltstahl writes:
> If org merely wraps in a `let`, it should not notice any of the multiple
> values
> business, because that is something done internally in `let-values`.
>
The "let", to define the org variables, ends up putting the "import"
inside the scheme expression, like this:
Hi Chris,
chris writes:
> Hi all,
>
> ```
> hello hello hello hello hello hello hello hello hello hello hello hello hello
> hello hello \(\text {hello hello hello hello hello hello hello hello}\)
> ```
>
> If you put the above text in a org file, and activate `visual-line-mode` and
> `o
Angel de Vicente writes:
> Hello,
>
> I was trying to export an .org file to .rst. I have ox-rst 20200815.1511
> installed, and I have run (require 'ox-rst), but despite this, there is
> no option for rsT in the Org Export Dispatcher. Did I miss something to
> make it work?
>
Maybe this know iss
pareto optimal writes:
> I found the only way to place the button where I wanted was to insert
> some blank space after the heading. Is that expected and best practice
> or is there some other way to do it?
FWIW, instead of inserting some blank spaces, you could overlay existing
characters, you'
Jens Lechtenboerger writes:
> On 2023-02-20, Bruno Barbier wrote:
>
> However, if I use insert-file-contents-literally with a unicode
> file, I do *not* have to set the coding-system-for-write. This just
> works:
>
>(with-temp-buffer
> (insert-file-contents-
Jens Lechtenboerger writes:
> On 2023-02-17, Bruno Barbier wrote:
>
>> Here is a way to reproduce that doesn't use org, in case it might help
>> to manully fix your encoding issue:
>>
>>(with-temp-buffer
>> (insert "Lechtenb\303\266rger
Jens Lechtenboerger writes:
> So, maybe my question is: Must text be decoded for Org mode from now on?
Yes. Since forever. Emacs must know how to read/write from/to files and
what text to display to you. Org is just relying on Emacs for that part.
Bruno
Jens Lechtenboerger writes:
> On 2023-02-17, Ihor Radchenko wrote:
>
>> Jens Lechtenboerger writes:
>>
>
>> Not a bug. You need to fix your files with improper encoding.
>
> The file has the proper encoding. I insert literally on purpose as
> stated above.
IIUC, the file has the proper encodin
Hi Jens,
Jens Lechtenboerger writes:
> ...
> Note that I insert contents literally because I do not want
> ‘find-file-hook’, automatic uncompression, etc. (which are avoided
> according to the doc string of insert-file-contents-literally).
>
> Could the old behavior be restored?
By using `ins
1 - 100 of 164 matches
Mail list logo
