On Mon, 30 May 2022 at 00:20, Ihor Radchenko wrote:
> It would be interesting to hear about the outcome and the student
> feedback.
>
> Best,
> Ihor
The workshop was by chat (Telegram), and only one student came. He
installed Emacs, Mpv, downloaded a copy with subtitles of the
eev-wconfig video,
Juan Manuel Macías writes:
> I believe that an html attribute to display marginal verse numbers in
> sequence could be useful for certain content, as philological texts
> (like here:
> https://en.wikisource.org/wiki/The_Iliad_and_Odyssey_of_Homer_(Cowper)/Volume_2/The_Odyssey/Book_I)
>
> The
Arthur Miller writes:
>> By "generic" I did not mean general-purpose all-functional framework.
>> We just need something to remove code duplication in
>> org-export-dispatch, org-agenda, org-capture, org-set-tags-command, etc
>> They all share pretty similar code to generate dialogues.
>>
>> As
Bastien writes:
>> Apparently nobody touched this for a very long time. The last change
>> in this area was 9 years ago.
>
> Indeed, it would be good to have someone as a maintainer. I suspect
> the code is stable is still useful to some users.
Should we create a help request for
Eduardo Ochs writes:
> I think that you are underestimating how alien eev is for most people.
> Let me suppose that what you mean by your comments is this:
>
> "I've spent N minutes watching this video - for N big - and I feel
>that I've learned very little! What is the best way to learn a
I applied the discussed two patches onto main via 1525a5a64 and
f6f26d4ce. The suggested amendments were incorporated.
> I do not like (unless (when ...)) composition. If I remember correctly,
> `when' should be used for side effects, so `and' may be more suitable
> here. Otherwise it looks
Ihor Radchenko writes:
> Arthur Miller writes:
>
>> Simplicity comes from the org-templates. Me, and I guess other people are
>> familiar with org-catpure templates already, and I mean, can it be simpler to
>> create a menu of choices then a simple list:
>>
>> '(("key1" "label1" exec (lambda ()
Ihor Radchenko writes:
> Yet, the information is surprisingly scattered. I was unable to find a
> single guide on the available possibilities. Mostly unanswered or
> partially answered questions from users.
Yes you're right. In addition, what I have been testing is not a panacea
either. In
Hi,
personally, I find tracking information through TODO keywords rather
unappealing. There are two
reasons: the first one is that you may loose information. For instance, if you
use "TO-READ", "To-
BUY", "READ" to track your books, does that mean that every item that is marked
"READ" is
Vladimir Nikishkin writes:
> This report is not about exporting Org code. It is perfectly fine that
> an empty line is required in org to demarcate a paragraph. The example
> above is just what I would imagine as an "ideal case".
> However, when `paragraph-indent-minor-mode` is turned on,
>
Ypo writes:
> If we find a typo, how should it be reported?
Yes! Thanks for this.
Fixed on main via a407a89c5.
> For example, in org footnote section:
>
> …This can be nil, to place footnotes locally at the end of the
> current outline node. **If** can also be the name of a special
>
Tor Kringeland writes:
> Maybe a function like that could be added to Org, that the user could
> add to `org-cycle-hooks' to produce the "opposite" of
> `org-cycle-hide-drawers'/does what `org-cycle' used to do without
> `org-cycle-hide-drawers' in the hook in Org 9.5?
I will take a note on
Juan Manuel Macías writes:
> Improving performance and compile time in TeX is an old topic, and there
> are a few tricks here and there. But TeX is what Emacs is, both are
> venerably old; and both are single-thread.
Yet, the information is surprisingly scattered. I was unable to find a
single
If we find a typo, how should it be reported?
For example, in org footnote section:
…This can be nil, to place footnotes locally at the end of the
current outline node. **If** can also be the name of a special
outline heading under which footnotes should be put.
Ypo writes:
> Thanks for your effort, Ihor
>
> But that code is so difficult for me, that I can barely understand it.
Well. The basic idea is to go through the document right before
exporting and replace all the comments with some kind of exportable
environment. Below is the working code that
Uwe Brauer writes:
> In any case thanks for both solution, that was very generous and helpful.
>
> Developers: why to include some of this code in a addon file, if Juan agrees
> of course!
A more canonical solution would be writing
org-export-filter-options-functions that set :output-file
Thanks for your effort, Ihor
But that code is so difficult for me, that I can barely understand it.
El 29/05/2022 a las 3:19, Ihor Radchenko escribió:
Ypo writes:
I wanted to export my # comments so I could share my notes with more people,
using HTML export. I would export all of them.
Paul Kaletta writes:
> I want to use Emacs bug-reference-mode together in my Org mode
> setup. Here's an example file:
>
>
> # Local Variables:
> # eval: (bug-reference-mode)
> # bug-reference-bug-regexp:
> "\\(\\(?:\\(?:SUPPORT\\|support\\)-\\)\\([0-9]+\\)\\)"
> #
Hi,
the https://orgmode.org/org-info.js file is available again, thanks
for reporting this.
Ihor Radchenko writes:
> Apparently nobody touched this for a very long time. The last change
> in this area was 9 years ago.
Indeed, it would be good to have someone as a maintainer. I suspect
the
Ihor Radchenko writes:
> I recently had a need to export org into multi-column latex and noticed
> that inlinetasks are exported into boxes that are wider than column
> width. That looks ugly.
>
> The attached patch fixes this.
Applied onto main via d37e4dc0f.
Best,
Ihor
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> From the backtrace, seems (buffer-file-name) returned nil, I guess you
>> first created a new buffer and have not saved it to file. That caused it
>> return nil. Not Org Mode problem. Not saving file is a common problem in
>> young
On 26/05/2022 11:23, Ihor Radchenko wrote:
diff --git a/lisp/org.el b/lisp/org.el
index d7da8efc4..45a179a8a 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -7975,7 +7975,12 @@ (defun org-open-file (path in-emacs line
search)
(when (eq cmd 'mailcap)
(require 'mailcap)
Ihor,
Your patch may be an improvement, but it requires an additional fix, see
below.
However, in my opinion, it does not address original Craig's issue. The
patch improves handling of *non-text* files requiring *external*
viewers, while Craig complained that behavior for shell script is
23 matches
Mail list logo
