Perhaps I'll try it, just for fun. I'm pretty happy with my layout and
theme, everything, but maybe I could get some ideas.
Thank you,
Alan
On Mon, Nov 29, 2021 at 7:39 AM Thomas S. Dye wrote:
> Aloha Alan,
>
> Alan E. Davis writes:
>
>
> > It is interesting that an old timer like yourself
Tim and all!
>> diff --git a/lisp/org.el b/lisp/org.el
>> index 1a1375461..fdeec0d67 100644
>> --- a/lisp/org.el
>> +++ b/lisp/org.el
>> @@ -19695,7 +19695,8 @@ non-nil."
>>(save-excursion (forward-char -1) (delete-horizontal-space))
>>(delete-horizontal-space)
Hi all,
I've started developing Babel support for Ada and SPARK languages.
I would like to include them in the main org-mode repository, as an
additional ("officially") supported language by org-mode.
Temporary development can be found at
https://github.com/rocher/ob-ada-spark/
For a new
Hi there,
Perhaps it's a bug, or something i don't understand, i post on reddit
(https://www.reddit.com/r/emacs/comments/r5yt4a/r_talking_with_python_using_orgtable_not_work/)
to see if people on org community know the problem.
I cross post here to see if it's a know bug or somethings ?
Hi,
I'm trying to take some notes and explain things (to myself, to
others). So org babel it is, yay!
This is my first (well, second: `:results value' turned up empty):
Blah, blah blah...
#+name: mklst/define
#+begin_src scheme
(define-syntax mklst
(lambda (s)
Sébastien Miquel writes:
> Rasmus Pank Roulund writes:
>>> This is most likely due to native compilation which compiles the
>>> unquoted lambda. Once compiled, it (presumably) fails to be passed to
>>> the external emacs process.
>> Ah, interesting. Is this a bug or a feature?
>
> I think the
Tim Cross writes:
> Well, that is the big question - why was
> org-comment-line-break-function added instead of just using the
> default comment-indent-new-line?
Looking back at commit d58d40f0c864ae3a6d7c66df34769619ad2486c1, I see
this comment was added by Nicolas (still in org.el):
;;
> Jeff Trull writes:
> Confirmed, after updating org it now works! Thanks for your help.
> On Tue, Nov 30, 2021 at 1:07 AM Colin Baxter wrote:
>> Hello Jeff
>>
>> You clock table works for me, including your missing rate of
>> 150. I attach a screen shot.
>>
Dear Joseph,
based on the error message there seems to be a problem with the
'curley-nil-on-bennet-spinoz' bibliography entry, is it possible that
it contains a 'year = nil' row? If yes then I don't think that is
well-formed, at least citeproc-el cannot currently parse it. Anyhow,
apparently I
The org-manual could use more practical examples, in my opinion.
How does one submit suggestions/edits?
On Wednesday, 1 Dec 2021 at 15:00, Juan Manuel Macías wrote:
> Anyway, for format chunks of text in export I think
> org-link-set-parameters is a good alternative to macros.
I also have a few links defined (used to have one for citing but no
longer needed) but macros seem to be my first
Dear Andras,
You are very probably right. I will have a look on this entry in my
default bibliography file.
The code
(let ((org-export-before-parsing-hook '(org-ref-csl-preprocess-buffer)))
(org-open-file (org-html-export-to-html)))
put in .emacs.d/personal/preload/myorgexport.el
On 30/11/2021 19:54, Ihor Radchenko wrote:
Max Nikulin writes:
Ihor, thank you for your work related to such issues. I had a hope to
thank you for the fix, but I faced a warning again in a bit modified
scenario. This time it is soft indent mode.
...
First letter of new heading must be a
Hi Jan,
On Wed, Dec 1, 2021 at 7:58 AM Eric S Fraga wrote:
> On Wednesday, 1 Dec 2021 at 13:21, Jan Ulrich Hasecke wrote:
> > How do you configure your emacs using current versions like org 9.5 but
> > at the same time avoiding problems with incompatible packages or newly
> > introduced bugs?
Dear John,
I must say that to export references in html with org-ref 3, I meet a
lot of problems (with LaTeX, it's fine).
I am using prelude emacs and GNU Emacs 29.0.50 .
Starting emacs --daemon, the code
(let ((org-export-before-parsing-hook '(org-ref-csl-preprocess-buffer)))
Hi all,
after happily using straight for quite a while I am currently frustrated by a
couple of problems.
In a different thread I asked about exporting citations, which does not
work for me at all.
Today I discovered that pamparam does not work anymore with an error
message mentioned here:
Hi Jan,
Not that I’m unsympathetic to your issues, however I must say that your email
seems to have little to do with Org, and this *is* the Org mailing list.
Perhaps you would be better served by something like emacs.stackexchange.com.
Jan Ulrich Hasecke writes:
> Hi all,
>
> after happily
On Wednesday, 1 Dec 2021 at 15:57, juh wrote:
> But then I can't get out, because:
>
> Key ("" to exit)
>
> What key is this?
What completion engine are you using? In selectrum, typing C-j at that
point finishes the completion. Other engines will differ. You might
also try up-arrow and RET.
Hello,
juh writes:
> thanks a lot.
>
> basic works
Good! We're getting close.
> but with csl I get:
>
> citeproc-style-parse: Opening input file: Datei oder Verzeichnis nicht
> gefunden, /usr/share/emacs/27.1/etc/org/csl/chicago-author-date.csl
>
> File or directory not found.
That's
Hello,
juh writes:
> I fixed this, updated to the newest org but still no rendering in no
> format.
>
> Thanks to all.
>
> I will give up for the moment and maybe come back again later.
For the record, with the following test.bib file:
--8<---cut
Am Wed, Dec 01, 2021 at 03:44:48PM +0100 schrieb juh:
> but with csl I get:
>
> citeproc-style-parse: Opening input file: Datei oder Verzeichnis nicht
> gefunden, /usr/share/emacs/27.1/etc/org/csl/chicago-author-date.csl
>
> File or directory not found.
>
> I tried to point
>
> #+csl_style:
Timothy writes:
> Hi Jan,
>
> Not that I’m unsympathetic to your issues, however I must say that your email
> seems to have little to do with Org, and this *is* the Org mailing list.
>
> Perhaps you would be better served by something like emacs.stackexchange.com.
>
> Jan Ulrich Hasecke writes:
Hello Jan,
I've extracted the org relevant bit from your post.
On Wednesday, 1 Dec 2021 at 13:21, Jan Ulrich Hasecke wrote:
> How do you configure your emacs using current versions like org 9.5 but
> at the same time avoiding problems with incompatible packages or newly
> introduced bugs?
Hello,
Kaushal Modi writes:
> I see that comment-indent-new-line was added to emacs in newcomment.el back
> in 2000. So I don't know why org-comment-line-break-function was added. May
> be Nicolas can comment more on that.
Sorry, I do not remember.
As pointed out in the thread, this function
Hello,
Timothy writes:
> Looking at https://orgmode.org/worg/dev/org-syntax.html, there isn't,
Yup, I forgot to update it.
> I have not yet confirmed what =KEYPREFIX= and =KEYSUFFIX= may contain,
> but as a starting point, any of the characters allowed in =KEY= except
> =@= plus whitespace
Hi Nicolas,
thanks a lot.
basic works
Am Wed, Dec 01, 2021 at 02:42:10PM +0100 schrieb Nicolas Goaziou:
> If I change the second line to "#+cite_export: csl" instead, with the
> external Citeproc Emacs library properly loaded, I get:
>
> (org et al. 2021, 45)
>
> org et al. (2021, 45)
>
>
>
Hi Eric,
Eric S Fraga writes:
> Very nice Juan! I would find this use of links quite useful.
Thank you. Yes, org-link-set-parameters is quite productive, and
addictive in occasions! :-): I also have link types defined for somewhat
extravagant things, such as linking videos and music from the
nil entries are not that uncommon in bibtex entries that are retrieved
with org-ref, especially for ASAP articles which typically have not been
assigned volumes, pages, etc. I usually put nil in as a placeholder so
that the empty fields don't get deleted when you clean the entry. They
are also
Jan Ulrich Hasecke writes:
> Hi all,
>
> after happily using straight for quite a while I am currently frustrated by a
> couple of problems.
>
> In a different thread I asked about exporting citations, which does not
> work for me at all.
>
> Today I discovered that pamparam does not work
Am Dienstag, dem 30. November 2021 schrieb Karl Voit:
> One of the next things I do have on my list is to try out crdt as
> I've learned at EmacsConf21 that it is mature enough to be used in
> practice.
>
> If that holds true, we can start dreaming of having a Etherpad-like
> session from our
Joseph Vidal-Rosset writes:
> Dear Andras,
>
> You are very probably right. I will have a look on this entry in my
> default bibliography file.
>
> The code
>
> (let ((org-export-before-parsing-hook '(org-ref-csl-preprocess-buffer)))
> (org-open-file (org-html-export-to-html)))
>
>
"christopher.pingitore" via "General discussions about Org-mode."
writes:
> Warning (emacs): org-element--cache: Cache corruption detected in
> 2021-08-08--Org File Test for Sharing--TECH.org. Resetting.
> The error was: (error "rx ‘**’ range error")
> Backtrace:
> nil
> Please report this to
Hi,
I've summarized my current state of mind about the whole Orgdown
fiasco into a blog article:
https://karl-voit.at/2021/12/02/Orgdown-feedback/
Don't worry, I tried to analyze my own faults as well so that others
might be able to learn from this unfortunate situation.
--
get
Jan Ulrich Hasecke writes:
> Today I discovered that pamparam does not work anymore with an error
> message mentioned here:
> https://github.com/nobiot/org-transclusion/issues/105
This most likely indicates that some third-party packages you use are
implementing risky Elisp practices known to
Karl Voit writes:
> Hi,
>
> I've summarized my current state of mind about the whole Orgdown
> fiasco into a blog article:
> https://karl-voit.at/2021/12/02/Orgdown-feedback/
>
> Don't worry, I tried to analyze my own faults as well so that others
> might be able to learn from this unfortunate
Hi Nicolas,
Thanks you for your feedback and clarifications. They were most helpful.
Thomas, I've also made a few tweaks based on your reply.
I've revised the draft in light of your comments, see below.
Citations follow the pattern
#+begin_example
[cite CITESTYLE: GLOBALPREFIX KEYCITES
Max Nikulin writes:
>> Well... I added yet another exception on main. Note that this special
>> case is also just in older Emacs versions.
>
> Ihor, have you pushed the change? I still can reproduce the issue with
> Emacs-26.3
Oops. I fixed Emacs 27, but apparently not Emacs 26. Should be
Thank you for writing all this down Karl. Thank you for your efforts and I
truly am sorry for everything you've been put through emotionally. I know
very well how a few particularly nasty comments can sap your energy as the
brain cycles on them over and over.
I hope you come out of this the
On Wednesday, 1 Dec 2021 at 22:17, M. ‘quintus’ Gülker wrote:
> There is Git, of course, but unless you are a programmer, using Git is
> pretty much arcane. I was not yet successful to explain Git to MS Word
> users, who are actually happy with the change tracking tooling Word
> has built in.
39 matches
Mail list logo
