kevinbanjo writes:
> I recently have been trying to build a website that has some embedded
> flowcharts created by mermaid and I'd really like them to be svg but
> orgmode only embeds the name of the image file and not the actual inline
> image in the exported html.
>
> How can I fix this?
Samuel Wales writes:
> tim cross, i would like to ask politely for you personally to
> henceforth please be VERY VERY careful when you say that i said or
> wanted something or tried to do something. i am not referring to this
> thread but general espeially in another thread.
apologies if
Timm Lichte writes:
> I'm trying to export org-agenda-files to a combined ics/icalendar file
> via org-icalendar-combine-agenda-files, but this fails due to unresolved
> links in the source files. Instead of fixing these links, is there any
> way to make org-export more robust and just ignore
Christian Moe writes:
> Consider the following minimal example, a nested list with a table in a
> sub-item (regardless of list types and empty lines):
>
> #+BEGIN_EXAMPLE
> 1. List item
>- Sub-item
> | Table |
> #+END_EXAMPLE
>
> This causes a format error on ODT export (I'm running Org
Hraban Luyat writes:
>> Is there any problem with the following?
>>
>>(alist-get :tangle params)
>
> This bit of code was moved, I didn't write it. The original code uses a
> variable `src-tfile' which isn't available here, so I reused the
> definition of that variable (which is (cdr
Max Nikulin writes:
>>> Please, do not use path components starting with dash, it is terrible
>>> for CLI tools. By the way, you promised underscores, not dashes.
>>
>> Why?
>
> It is inconvenient in interactive sessions (in scripts appropriate
> measures must be taken anyway), the following
Hi everyone.
I recently have been trying to build a website that has some embedded
flowcharts created by mermaid and I'd really like them to be svg but
orgmode only embeds the name of the image file and not the actual inline
image in the exported html.
How can I fix this?
TIA,
-Kevin
tim cross, i would like to ask politely for you personally to
henceforth please be VERY VERY careful when you say that i said or
wanted something or tried to do something. i am not referring to this
thread but general espeially in another thread.
Hi,
Consider the following minimal example, a nested list with a table in a
sub-item (regardless of list types and empty lines):
#+BEGIN_EXAMPLE
1. List item
- Sub-item
| Table |
#+END_EXAMPLE
This causes a format error on ODT export (I'm running Org version
9.5.4). In the content.xml
On 8/3/22 11:55 AM, Max Nikulin wrote:
>> + (when bare
>> +(if (and org-babel-tangle-use-relative-file-links
>> + (string-match org-link-types-re bare)
>> + (string= (match-string 1 bare) "file"))
>> +(concat "file:"
>> +
Hi, Uwe,
I also get an error when exporting my suggestions to ODT with the
official ODT exporter, but it's not because of the solutions. They
should all be fine, but anyway, it's enough that one of them works for
you.
Rather, the exporter seems to be confused by the way I mixed tables into
a
Hello!
I would like to know if there is an "Org" way of doing this with the
beamer export:
#+begin_src latex
* Section
** Sub-section
*** Slide
figure block
#+latex: \includegraphics<2->[height=0.5\regheight]{example-image-a}
#+end_src
That is: replacing the =#+latex:= line with a
Hi,
I'm trying to export org-agenda-files to a combined ics/icalendar file
via org-icalendar-combine-agenda-files, but this fails due to unresolved
links in the source files. Instead of fixing these links, is there any
way to make org-export more robust and just ignore the links? As far I
On 10/08/2022 20:23, Ihor Radchenko wrote:
Max Nikulin writes:
+the path."
+ (if (< (length id) 3)
+ (format "--/%s" id)
Please, do not use path components starting with dash, it is terrible
for CLI tools. By the way, you promised underscores, not dashes.
Why?
It is inconvenient in
Tom Gillespie writes:
>
> As mentioned above, I also like this approach. We could create a hack
> to work around the missing package metadata field, which would cause
> a failure when trying to build on emacs < 26 unless org-i-know-what-i-am-doing
> or some such is non-nil. The error message
Max Nikulin writes:
> On 10/08/2022 18:43, Ihor Radchenko wrote:
>> Ihor Radchenko writes:
>>
>> I have updated the patch to use "__/id" when id is too short.
>> Any objections?
>>
>> +When ID is too short (less than 3 chars), use its md5 hash to create
>
> Misleading docs, you do not use md5.
>
>
> I suggest to set description to nil and thus ask the user in such
> scenario.
>
I'm fine with that. Alternatively the default may be the target or custom
id (that is, the same that is in the link part), again letting the user
change it. Thanks!
Best regards,
Carlos
On 10/08/2022 18:43, Ihor Radchenko wrote:
Ihor Radchenko writes:
I have updated the patch to use "__/id" when id is too short.
Any objections?
+When ID is too short (less than 3 chars), use its md5 hash to create
Misleading docs, you do not use md5.
+the path."
+ (if (< (length id) 3)
+
Bastien writes:
> Tim Cross writes:
>
>> Therefore, I think the position should be that once an emacs version is
>> no longer one of the supported versions (current stable Emacs release
>> plus two previous major versions), there is no guarantee we will inform
>> the list when compatibility is
Tom Gillespie writes:
>> (while (process-live-p process)
>> (accept-process-output process)))
>
> When I tried this before it didn't work, but now it does, I
> must have missed something. Patch updated accordingly.
>
> The order in which the man.el code does things is supremely
> confusing,
Ihor Radchenko writes:
>> Ihor, I am afraid of collisions due to short input to md5. Long hash
>> value gives false impression of high entropy but actually there are not
>> so many variants for 1 or 2 characters strings. Either there is no point
>> in making long name from short id or random
alain.coch...@unistra.fr writes:
> When my .emacs contains only the following:
>
> (custom-set-variables
> ;; custom-set-variables was added by Custom.
> ;; If you edit it by hand, you could mess it up, so be careful.
> ;; Your init file should contain only one such instance.
> ;; If there is
On Wednesday, 10 Aug 2022 at 15:10, Ihor Radchenko wrote:
> Please report to ESS devs.
Will do. Thanks.
--
: Eric S Fraga, with org release_9.5.4-720-g4db67d in Emacs 29.0.50
Hello.
When my .emacs contains only the following:
(custom-set-variables
;; custom-set-variables was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work
"Fraga, Eric" writes:
> Debugger entered--Lisp error: (wrong-type-argument symbolp
> ((inferior-ess-primary-prompt . "\\w*> ") (inferior-ess-secondary-prompt)
> (inferior-ess-prompt . "\\w*> ") (ess-local-customize-alist .
> ess-julia-customize-alist) (inferior-ess-program .
25 matches
Mail list logo
