mpiled files in newer Emacs versions? If so, it's useful to have
major-version specific package-user-dir 's.
--
Kaushal Modi
etq package-user-dir (let ((elpa-dir-name (format "elpa_%s"
emacs-major-version))) ;default = "elpa"
(file-name-as-directory (expand-file-name
elpa-dir-name user-emacs-directory
--
Kaushal Modi
t/commit/?id=24acb31c04b4048b85311d794e600ecd7ce60d3b
See this new node in Emacs manual: (emacs) Early Init File
PS: Why does your email not remain in to: or cc: when I do Reply All? Is it
OK if it is left out in the future? I have been adding your email back in
manually.
--
Kaushal Modi
‘org-get-tags-at’ is an obsolete function (as of
Org 9.2); use ‘org-get-tags’ instead.
What's the canonical way to deal with such cases?
Thanks.
Kaushal
--
Kaushal Modi
On Mon, Apr 23, 2018 at 12:02 PM Kaushal Modi
wrote:
> But ox-hugo still compiles with this warning with Org 9.2:
>
> In org-hugo--get-tags:
> ox-hugo.el:1371:6:Warning: ‘org-get-tags-at’ is an obsolete function (as of
> Org 9.2); use ‘org-get-tags’ instead.
>
> What&#
nings'.
>
That's good to know. For now, I am using the macro-method to make ox-hugo
use the correct function for fetching inherited tags.
Thanks.
--
Kaushal Modi
; portion is hidden?
Would footnotes serve better? (I'm not a consumer of inline todos (yet?) so
consider this suggestion with a grain of salt :))
=
some text[todo:1]
* Inline TODOs (special heading like Footnotes)
[todo:1]: My todo
=
> --
Kaushal Modi
and exported to Markdown using ox-hugo which live right along the
old Markdown content... and everything just works.
> I really recommend ox-hugo, Kaushal has done a fantastic job and he is
> also really helpful and responsive with questions.
>
Thanks for this heavy recommendation. W
Hi all,
I normally am all for adapting to changes, staying on bleeding edges of
emacs, Org, etc.
But FWIW, for this particular change to the "
"header
> argument". A half-decent completion mechanism will display all of them.
>
Thanks for that tip! I guess I need to use the "i" approach more often than
the plain old C-s. But I confirm that with "i" followed by "header
argument", it presents a nice list of all arguments in the Ivy interface.
Kaushal
--
Kaushal Modi
rict what I'd like to do?
>
Hugo Go templating is very powerful[3]. It inherently has no restrictions.
The templating language does not have a "blog focus".
If you decide to use a theme, just as is[*], then that's a restriction. I
would suggest to pick a theme that best fits
Hello Thomas,
I forgot to expand a bit on this part..
On Fri, May 4, 2018 at 9:43 AM Kaushal Modi wrote:
>
>
>> I use org-mode for writing these kinds of thing now, and
>> I'm hoping to work out a way to make my org mode source work with
>> Hugo.
>&g
(match-beginning 2))
(org-table-delete-column)
(beginning-of-line)))
=
On Tue, May 3, 2016 at 12:57 PM Kaushal Modi wrote:
> Thanks Michael!
>
> That solution works great! I followed the discussion that followed in that
> thread and have adopted the following solution i
don't believe this happened before.
> > Any ideas?
> > Is this a recent org-mode change?
>
> I see this, too.
>
What do you guys see when you do C-u C-x = (equal sign is part of that
binding) with point placed on each of those differently colored "DONE"
states?
--
Kaushal Modi
e hl-todo package. But looks like you do, and it somehow
highlights only some "TODO" keywords based on some regexp.
How about disabling hl-todo completely in Org files, and then see if you
still get that difference in faces?
--
Kaushal Modi
keywords will make it
difficult for 3rd party Org parsers to adopt them too, resulting in even
lesser Org adoption.
I like Nicolas' idea where display properties are used to replace the
English keywords with the translation; that way the actual Org source
remains untouched.
> --
Kaushal Modi
Org keywords like HUGO_BASE_DIR, HUGO_SECTION, HUGO_BUNDLE.
Here's where ox-hugo works sort of like ox-publish.
What ox-hugo devs/users have to say on this?
>
Hope that helps clarify the differences.
Kaushal
> --
Kaushal Modi
orgzly/org-java
- Python-based Org parser to generate blog:
https://github.com/novoid/lazyblorg
- many more:
https://github.com/search?utf8=%E2%9C%93&q=org+mode+parser&type=
--
Kaushal Modi
mented style.
I would say that the "fn"-style footnotes remove any kind of ambiguity..
--
Kaushal Modi
25/ox-hugo.el#L2239-L2363
If this feature is approved for addition to ox-html, I can make a formal
patch where instead of looking for "---", I look for the appropriate string
based on the value of (plist-get info :with-special-strings).
Thanks!
Kaushal
--
Kaushal Modi
Hi Aaron,
Thanks for the feedback.
On Thu, May 24, 2018 at 1:42 PM Aaron Ecay wrote:
> Hi Kaushal,
>
> It seems like a good idea. My two comments are:
>
> - Remember that ox-html can export to HTML4, so the code would need to
> detect that case and have a sensible fallba
Hello Aaron,
On Thu, May 24, 2018 at 2:08 PM Kaushal Modi wrote:
> Expanding on your idea.. what if we had another Special block with name
> summary?
>
> #+begin_details
> #+begin_summary
> Open for details
>
> More summary.
> #+end_summary
> Many details here.
plemented as a before-parsing-hook
> that transforms the --- into the above syntax.
>
+1
> PS Once upon a time, I created ox-extras in contrib as a home for little
> snippets like this hypothetical before-parsing-hook. It never really
> took off, but maybe itʼs just biding its time...
>
Sure thing :)
--
Kaushal Modi
Hi Aaron,
I just went ahead and removed that "---" syntax from ox-hugo. Updated links:
1. https://ox-hugo.scripter.co/doc/details-and-summary/
2. https://ox-hugo.scripter.co/test/posts/details-and-summary/
(it was easy as I had committed that feature just yesterday.)
On Thu, May 24, 2018 at 3:0
s users).
>
That's a possibility. But as I said above, there isn't a strong reason to
have Hugo blog post source in HTML.
If the set of QOL improvements is empty, then the custom backend would
> disappear entirely. Less code for the same features = maintenance win in
> my book. YMMV of course...
>
Thanks.
--
Kaushal Modi
ring-match "\\(?1:open\\(?2:=\"\\(?3:t\\)\"\\)\\)"
attr-str)
(if (match-string 3 attr-str) ;if attr-str contains `open="t"'
(setq attr-str (replace-match "" nil nil attr-str 2))
(setq attr-str (replace-match "" nil nil attr-str 1))
--
Kaushal Modi
.
Just putting this custom figure.html in your site's layouts/shortcodes/
directory (which will override the inbuilt figure shortcode) will fix this
second issue.
Hope this helps. For future, you can ask ox-hugo questions directly at
https://github.com/kaushalmodi/ox-hugo/issues.
I don&#x
re is no problem.
>
Correct. That is intended. You need htmlize installed if you have export
elements that need fontification/syntax highlighting, like code blocks.
> --
Kaushal Modi
O) to
that heading.
--
Kaushal Modi
Hi Nicolas,
On Thu, Jun 14, 2018 at 10:53 AM Nicolas Goaziou
wrote:
>
> FWIW, I cannot reproduce it.
>
I cannot reproduce that either (after emacs restart).. sorry for the noise.
(Now I wonder what happened last time..)
--
Kaushal Modi
missing tests). Should I format it
w.r.t to next? or master?
Thanks.
=
>From 8572f66a514289e2193f162f8c3c24818af00912 Mon Sep 17 00:00:00 2001
From: Kaushal Modi
Date: Wed, 21 Mar 2018 11:41:51 -0400
Subject: [PATCH] Make `org-meta-return' do the right thing for checkbox
li
you are on a "- foo" line, M-RET creates "- " on the next line.
- *But* if you are on a "- [ ] foo" line, M-RET still creates "- " instead
of "- [ ] " on the next line?
Shouldn't M-RET and M-S-RET behavior be switched for checkbox lists?
--
Kaushal Modi
symmetric with M-RET and M-S-RET on headlines. E.g., in
> the following document
>
> * TODO Stuff|
>
> where "|" is point, M-RET results in
>
> * TODO Stuff
> *
>
> i.e., no TODO added. I find it straightforward.
>
OK. So no one way is right :) So it makes sense to keep it as it is.
--
Kaushal Modi
luates before you do Org exports, and then
simply use this in your Org files:
#+macro: keys (eval (my/org-macro-keys-code $1))
{{{keys("Ctrl c Ctrl e H H")}}}
PS: Thanks for sharing that code! You are following the vision of ox-hugo..
replacing Hugo shortcodes with Org macros :+1: :)
--
Kaushal Modi
sc) link-1)))
(concat "[[http://www.hammerspoon.org/docs/"; link-1 "][" desc-1 "]]")))
In your Org file:
#+macro: hsapi (eval (my/org-macro-hsapi-code $1 $2 $3))
{{{hsapi(hs.notify)}}}
{{{hsapi(hs.notify,show)}}}
{{{hsapi(hs.notify,show,Foo)}}}
--
Kaushal Modi
e nothing but {{{val1}}}{{{val2}}}.
> ...
>
Org macros don't get evaluated inside src blocks as far as I know. But
Noweb might help you. Look for this feature in Org manual. I use Noweb as
"macros for src blocks".
> --
Kaushal Modi
i:
1. Item 1.
2. [@10] Item 10.
--
Kaushal Modi
with.
>
So, what is the question? :)
Looking at just "Org" and "Android phone", I can suggest the Orgzly app.
It can sync notes to a directory on your phone, and you can sync that dir
to your computer via USB if you like (I like the Dropbox sync option).
--
Kaushal Modi
On Thu, Sep 13, 2018 at 11:28 AM Glenn Morris wrote:
>
> Emacs already includes htmlfontify, since 23.2.
> Is there some obstacle to Org using that? (bug#7506)
This has been discussed before on the Org mailing list.
>From what I remember, there is not objection to use that instead; it's
just tha
Hello,
On the topic of xdg, I pulled Org from main branch today and tried to build
it but it's failing with:
org-persist.el:32:1:Error: Cannot open load file: No such file or
directory, xdg
Anybody else seeing this?
On Fri, Nov 5, 2021 at 9:27 AM Kaushal Modi wrote:
> Hello,
>
> On the topic of xdg, I pulled Org from main branch today and tried to
> build it but it's failing with:
>
> org-persist.el:32:1:Error: Cannot open load file: No such file or
> directory, xdg
>
> Any
On Fri, Nov 5, 2021 at 9:27 AM Kaushal Modi wrote:
> Hello,
>
> On the topic of xdg, I pulled Org from main branch today and tried to
> build it but it's failing with:
>
> org-persist.el:32:1:Error: Cannot open load file: No such file or
> directory, xdg
>
> Anyb
)
org-persist-write((org-element--headline-cache org-element--cache)
#)
org-persist-write-all(#)
org-persist-write-all-buffer()
kill-buffer("NEWS")
Are there any pointers on how to fix this?
Thanks!
--
Kaushal Modi
On Fri, Nov 5, 2021 at 10:25 AM Ihor Radchenko wrote:
> Fixed on main. Thanks for reporting!
>
Thanks! I confirm the fix.
On Fri, Nov 5, 2021, 9:48 AM Ihor Radchenko wrote:
>
> I am not sure if we are dropping Emacs 25 just yet. However, there is
> currently more than one place in Org that does not work on Emacs 25.
> See https://list.orgmode.org/87zgqu6081.fsf@localhost/T/#t
>
> If compilation is critical for you,
Hello all,
I am following up on this issue with ob-shell and sessions.
I had posted the recipe to reproduce the issue few months back, and it
still applies; ref:
https://list.orgmode.org/CAFyQvY2AeToQc2G=e+de4votetfbkvisenipypw1y-feu1o...@mail.gmail.com/
Thanks!
--
Kaushal Modi
On Tue, Nov 30, 2021 at 3:20 PM Marco Wahl wrote:
>
>
> 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))
On Tue, Nov 30, 2021, 6:29 PM Tim Cross wrote:
>
> Regardless, I think that unless we understand the purpose of
> insert-before-markers-and-inherit, we should make the patch such that it
> still calls that function. Even if fill-prefix is nil there is
> probably a good reason why the markers and
that.
So would this patch work?
=
>From 1a9187b82ed8d4e8d54ddd369a44d34295281fc3 Mon Sep 17 00:00:00 2001
From: Kaushal Modi
Date: Tue, 30 Nov 2021 20:37:10 -0500
Subject: [PATCH] org: Remove `org-comment-line-break-function'
* lisp/org.el: Remove `org-comment-line-break-function&#x
On Thu, Dec 2, 2021, 8:08 AM Vincent Breton
wrote:
> Hi,
>
>
> Emacs and Emacs Org documentation, and lot of others GNU products use
> Texinfo to generate their own documentation to different formats.
The Org mode documentation switched to Org format few years back:
https://git.savannah.gnu.or
On Sat, Dec 4, 2021, 5:25 PM Tim Cross wrote:
>
> Given that Nicholas cannot remember the reason for the original function
> and suspects it was meant to be an internal only function, I think this
> patch is probably the best way forward and should be applied.
>
Thanks. Nicolas asked me to add t
allow external ssh access.
>From de607dff518eaa91149ff1aa8c255f67fb6ee887 Mon Sep 17 00:00:00 2001
From: Kaushal Modi
Date: Tue, 30 Nov 2021 20:37:10 -0500
Subject: [PATCH] org: Remove `org-comment-line-break-function'
* lisp/org.el: Remove `org-comment-line-break-function' and
On Sun, Dec 5, 2021 at 4:12 AM Nicolas Goaziou
wrote:
> Hello,
>
> Ihor Radchenko writes:
>
> > Sorry, but tests are still slow for me after the update.
> > If I run the test from inside Emacs with ert, things got better, but
> > make BTEST_RE="^test-org-cite/adjust-note" test
> > still takes 12
On Mon, Nov 8, 2021 at 1:05 AM Ihor Radchenko wrote:
>
> I was able to reproduce the issue. This is a bug on ox-hugo side.
> `org-hugo--get-pre-processed-buffer' inserts text with
> inhibit-modification-hooks bound to non-nil, which breaks
> org-element-cache. The cache is enabled by default in l
On Wed, Dec 15, 2021 at 9:29 PM Kaushal Modi wrote:
>
> Can you help fix this?
>
Also looking closely, I am seeing a different warning:
Warning (org-element-cache): org-element--cache:
(org-hugo-export-wim-to-md) Cached element is incorrect in *Ox-hugo
Pre-processed ox-hugo-manua
> Can you:
> 1. Update Org to latest version
> 2. set org-element--cache-self-verify to 'backtrace
> 3. set org-element--cache-self-verify-frequency to 1.0
> 4. Try to reproduce the warning you are seeing
> 5. If you still see it, post the full warning text including the
>backtrace (below the w
On Thu, Dec 16, 2021 at 10:16 AM Ihor Radchenko wrote:
>
> FYI, it is suspicious. You should be at 9.5.1. Maybe you forgot to make
> clean; make autoloads.
>
I actually run a wrapper script to update Org and that has all that:
=
# cmds to update to latest commit on git main branch
#
On Fri, Dec 17, 2021 at 11:34 PM Ihor Radchenko wrote:
> > There's a setup included in there; I forgot about that. If you don't mind
> > trying it again, this would download everything needed:
>
> Thanks! I was able to follow your steps this time.
>
I really appreciate making this extra effort t
enables the verbatim mode (prevent Org from
replacing the Org entities, do the sub/superscript expansion, etc.)?
--
Kaushal Modi
On Thu, Jan 6, 2022 at 1:27 PM Juan Manuel Macías
wrote:
> I think one possibility would be using a parse tree export filter:
>
> #+BIND: org-export-filter-parse-tree-functions (katex-verbatim)
> #+begin_src emacs-lisp :exports results :results none
> (defun katex-verbatim (tree backend info)
>
On Thu, Jan 6, 2022 at 2:33 PM Juan Manuel Macías
wrote:
> I just realized that there is a much simpler solution for your katex
> environment :-)
>
> You can use an example block, and define your custom environment using
> the attribute :environment
Sorry, but this exporter is derived from md, an
> What am I missing?
>
> It seems like you want your derived backend to transcode special blocks
> somewhat differently than the parent backend. And adding a special block
> export filter doesn't quite do the job.
I tried out the example Juan posted and it works perfectly well. But
it would requ
On Sat, Jan 8, 2022 at 10:01 PM Berry, Charles wrote:
>
>
> A simple one here:
>
> #+begin_src emacs-lisp
> ;; minimal backend with latex parent
> (org-export-define-derived-backend 'newlatex 'latex
> :translate-alist
> '((special-block . org-newlatex-special-block)))
>
> ;; special
> On Sat, Jan 8, 2022 at 10:01 PM Berry, Charles
> wrote:
Hi Charles,
I used your minimal example to show the issue I am seeing when using
ox-md as the base exporter.
=
#+property: header-args :results none :exports none :eval never-export
#+options: toc:nil
* Define newmd
On Sun, Jan 9, 2022 at 3:01 PM Nicolas Goaziou wrote:
>
> I suggest to use
>
> (org-element-interpret-data (org-element-contents special-block))
That does it!! Thank you!
Also thanks to Juan and Charles who helped lead me to the final solution.
On Mon, Jan 10, 2022 at 8:35 AM Timothy wrote:
>
> FWIW, I think it would be good to be internally consistent. #+RESULTS is
> currently one of the few keywords inserted in upper case. Unless there’s a
> good
> reason to distinguish it from other keywords (perhaps an argument could be
> made
> th
cache to nil, Emacs stopped hanging.
Looking at your bug report, I believe that the issue I am seeing with
cache and Org tags could be very much related. So thanks for
submitting this.
--
Kaushal Modi
Hello Ihor,
> The issue here had nothing to do with hanging. You are probably seeing
> yet another bug.
ok.
> By hang, do you mean that even C-g does not restore responsiveness?
Typically, within a second of doing C-c C-q, I would know that the
buffer is going to freeze, and if I do C-g soon en
Rendering/prettifying the website using CSS, templating, etc in a
static site generator.
Of course you can do everything in Org mode and many people do it, but
then you need to design CSS, JS, etc yourself.
( I am not a web designer, so I took the static site generator
approach and started learning more about CSS and templating from
available themes. )
Kaushal
Emacs version: GNU Emacs 28.0.91 (build 7, x86_64-pc-linux-gnu, GTK+
Version 3.22.30, cairo version 1.15.12) of 2022-01-25, built using
commit 7eca80b20444f7bd7bcb6a66a9054e029f0e7013.
--
Kaushal Modi
On Sun, Feb 13, 2022, 4:18 AM Jeremie Juste wrote:
> Hello Cash,
>
> Many thanks for reporting but I cannot reproduce the error with my current
> version of emacs and org-mode. Could you specify the version of org-mode
> and emacs you are currently using?
>
> * test
> :PROPERTIES:
> :ID: cb
Hello Nicolas,
> Since you are probably busy, I implemented this on your behalf. The new
> behaviour is in main branch. Thank you.
>
Can this commit[1] be merged into the main branch. Locally on my
machine, I use org built from main and something like this was working
fine:
#+cite_export: csl ci
> It is already in the main branch, AFAIU. I assume you mean it should be
> back-ported to bugfix branch. If that's the case, I don't know. This is
> a new feature, and not a critical one: there are workarounds, as you
> found out.
Yes, sorry, I meant the bugfix branch.
> This should be available
On Tue, Feb 22, 2022, 12:34 AM Ihor Radchenko wrote:
>
> I am wondering if many people in the list experience latency issues.
> Maybe we can organise an online meeting (jitsi or BBB) and collect the
> common causes/ do online interactive debugging?
>
+1
I have seen few people see this issue on
On Wed, Feb 23, 2022 at 7:37 AM Ihor Radchenko wrote:
>
> Dear all,
>
> Since there is at least a couple of people who might be interested, lets
> try to meet online on jitsi and debug performance issues you experience
> because of Org mode. Probably some time this Saturday (Feb 26). I am
> thinki
On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey wrote:
>
> Hej,
>
> I have noticed that properties that stretch over multiple lines using
> the :value+: syntax are ignored by org-element-property and therefore
> also by e.g. org-export-get-node-property when exporting to ics via
> ox-icalendar.el (se
On Mon, Feb 28, 2022 at 3:34 PM Kaushal Modi wrote:
>
> On Sat, Oct 2, 2021 at 11:03 AM Hanno Perrey wrote:
> >
> > Hej,
> >
> > I have noticed that properties that stretch over multiple lines using
> > the :value+: syntax are ignored by org-element-propert
is in a list but doesn't wrap
- abcdefg abcdefg abcdefg abcdefg `[[abc def][bar]]'.
=
Note that incorrect export of the inline src block in section 1 above.
The remaining sections exports correctly because either the inline src
block is not in a list item, or it doesn't wrap to the next line.
--
Kaushal Modi
Hello Christian,
tl;dr: If you decide to learn how to use Hugo (read its docs, ask questions
on its forum, etc.), this[1] should solve the issues you have faced so far.
---
Details:
On Fri, Mar 11, 2022 at 7:04 AM wrote:
>
> ox-hugo with hugo is often mentioned in the context. But ox-hugo is
On Sun, Mar 13, 2022, 8:23 AM wrote:
> In real I (try to) use ox-hug to export my org-files (org-roam-v2) to
> markdown (and later to HTML).
>
> After analyzing the my debug output [1] the ox-hugo people pointed me to
> org-roam community because the error is "thrown" (correct term in
> emas-lisp
On Sun, Mar 13, 2022, 6:55 AM Sébastien Gendre wrote:
> Hello everyone. _o/
>
> When I export an Org file to LaTeX and finally PDF, the code blocks and
> quotes often exceed the width of the page.
>
Hello _o/
I fixed[1] that problem by using the LaTeX minted package that allows
wrapping around
e has been there at least since 2015.
Thanks!
--
Kaushal Modi
Hello,
Just pinging here again. Can someone confirm this bug?
--
Kaushal Modi
On Tue, Mar 1, 2022, 10:10 PM Kaushal Modi wrote:
> Hello,
>
> I believe I have come across a corner case issue where the inline src
> block element doesn't get parsed as one, if:
>
> 1. That
On Sun, Apr 3, 2022, 4:29 PM wrote:
> Hello togehter,
>
> is it usual to have auto-fill-mode (automatic new-line after n
> characters) turned on in org or org-roam (including fill-column set e.g.
> to 80)?
>
I cannot comment on that. Enabling auto-fill-mode is user preference.
Or let me ask fro
On Mon, Apr 4, 2022, 12:06 AM Ihor Radchenko wrote:
>
> I think your examples are a bit misleading.
I have the indentations correct in my three examples.
A list item continues until
> there are _2_ blank lines or until the subsequent line is not indented >=
> current list item indentation:
>
On Mon, Apr 4, 2022 at 10:34 AM wrote:
>
> I would like to know why does a list need 2 blank lines instead of 1?
> For what reason exists this rule?
>
- 1 blank line in a list item with create a paragraph break as I showed in
my example earlier. It will not end the list item or list.
- So we nee
On Thu, Apr 7, 2022 at 12:30 PM William Denton wrote:
> I'm using macros to format names in a LaTeX export, like so:
>
> on export and LaTeX will format it. That works fine. But in an index of
> names,
> if I want
>
> {{{m(Denton, William)}}}
>
> then Org takes that as two arguments to the macr
that "[[info:(org)
External Links]]" would work as well. But I think I am missing out on
some flow that would make the above manually editing in step 3
unnecessary.
How do you insert info: links efficiently?
--
Kaushal Modi
On Mon, Apr 11, 2022 at 8:35 AM Kaushal Modi wrote:
> I believe I am missing out something basic with inserting info: links
> in Org documents.
Yes, I was missing out on something :)
To my future self:
1. When in Info buffer, do M-x org-store-link (typically a user binds
this to C-c l:
On Mon, Apr 11, 2022 at 10:53 PM Vikas Rawal wrote:
>
> For a major project like this, I would just put these in a separate file, and
> include it using #+INCLUDE:
Org has a special keyword for the purpose of including *just the setup
stuff*: #+setupfile
See (org) Export Settings.
#+include is
On Mon, Apr 11, 2022 at 10:57 AM Max Nikulin wrote:
> There are a some problems with info links outside of Emacs:
> - Export to PDF
Yeah, I recently realized that I will need to add custom support for
exporting info: links using ox-hugo. I made a small blog post out of
this learning: https://scr
On Wed, Apr 13, 2022 at 7:38 AM Max Nikulin wrote:
>
> On 13/04/2022 01:26, Kaushal Modi wrote:
> > On Mon, Apr 11, 2022 at 10:57 AM Max Nikulin wrote:
> >
> >> There are a some problems with info links outside of Emacs:
> >> - Export to PDF
> >
> &g
ring= lang "elisp")) (cond ((and (boundp ...)
(fboundp ...) (fboundp ...)) (let (...)
(eldoc-print-current-symbol-info))) ((fboundp
'elisp-eldoc-documentation-function)
(elisp-eldoc-documentation-function)) (t (let
(eldoc-documentation-function) (eldoc-print-current-symbol-info)
((or (string= lang "c") (string= lang "C")) (if (require 'c-eldoc nil
t) (progn (c-eldoc-print-current-symbol-info ((string= lang "css")
(if (require 'css-eldoc nil t) (progn (css-eldoc-function
((string= lang "php") (if (require 'php-eldoc nil t) (progn
(php-eldoc-function ((or (string= lang "go") (string= lang
"golang")) (if (require 'go-eldoc nil t) (progn
(go-eldoc--documentation-function (t (let ((doc-fun
(org-eldoc-get-mode-local-documentation-function lang)) (callback (car
args))) (if (functionp doc-fun) (progn (if ... ... ...
org-eldoc-documentation-function(#f(compiled-function (string &rest
plist) #))
=
Recipe to create this error:
1. Create a file test.org with these contents:
#+begin_src org
,#+html: foo
#+end_src
2. emacs -Q
3. Load/evaluate org-eldoc.el from
https://git.sr.ht/~bzg/org-contrib/tree/master/item/lisp/org-eldoc.el
4. Open the test.org file and place the point *inside* the org src block
5. eldoc error: (error Lisp nesting exceeds ‘max-lisp-eval-depth’)
-
Upon inspecting the `org-eldoc-documentation-function` function, I
don't see a reason why the control should enter the default of `t'
case if the src lang is "org". Just returning with nil works for me if
the lang is "org". I will send a patch for this in a follow-up email.
--
Kaushal Modi
-indent, untabify
patch 2: Fix for the inf-loop
Can someone please review and apply these patches to the org-contrib repo?
[I am unable to commit using ssh/git: protocol (only https is allowed)
based on the network restrictions at work.]
Thanks!
--
Kaushal Modi
0001-lisp-org-eldoc.el-Whitespace
On Fri, Dec 17, 2021 at 11:34 PM Ihor Radchenko wrote:
>
> Kaushal Modi writes:
>
> > I actually run a wrapper script to update Org and that has all that:
> > ...
> > I verified that at least the git hash was latest as of then:
> > release_9.5-364-g*de022e*
>
-style to overlays, and refresh that Org
buffer, I see the square brackets around asdf in the src block (as
expected).
Org mode version 9.5.3 (release_9.5.3-458-g1ed9e4)
--
Kaushal Modi
On Thu, Apr 28, 2022 at 10:44 AM Ihor Radchenko wrote:
> I am not going to fix this just yet unless it is critical. It does not
> look like this bug is common.
It's not time-critical, but it would be good to fix this bug. It's not
just the Org link syntax.. any Org markup is fontified inside the
On Thu, Nov 25, 2021 at 6:21 AM juh wrote:
> With cite_export: basic I get
>
> Wrong value for ENTRY-OR-KEY: nil
Hello,
I saw the ox-hugo CI fail with emacs master (29.0.50) over the past
few days with this backtrace, but this error is probably not related
to ox-hugo, and I need help confirming
On Mon, May 9, 2022 at 10:21 AM Kaushal Modi wrote:
> Can someone using emacs
> built from master branch confirm that they see this same error when
> `org-cite-process-bibliography` is called? It should be reproducible
> without using ox-hugo too.
Alright I was able to confirm t
I have now sent this to Emacs bug tracking:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55342
701 - 800 of 857 matches
Mail list logo
