Re: Unable to get current or via use-package
Hi João, João Pedro de Amorim Paula writes: > On 18 February 2022 18:32, João Pedro de Amorim Paula > wrote: > >> I ended up not posting the link[1] I referred to in the first e-mail, > > Welp, seems like I did it again... But no harm done this time, all the > necessary code was attached anyway :P > > Forgetfully, Thanks for the code. I'll have a look at it. Cheers, Loris
Re: How to enforce sub-scripts with {} only for HTML export?
On 2022-02-20 23:29, Greg Minshall wrote:
Edgar,
one of my .org files has this
# ^:{}: disable super/subscripting:
https://stackoverflow.com/a/698791/1527747
#+options: ^:{}
ymmv.
Thank you, Greg. Sometimes I need to export sub-headings, selected text
or included files, and the variable gets overridden. Thanks a lot :) .
-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
Re: How to enforce sub-scripts with {} only for HTML export?
On 2022-02-20 21:49, Kyle Meyer wrote:
{} should be a symbol. Try
(setq org-export-with-sub-superscripts '{})
Thank you!!!
-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
Re: Question Regarding Creating HTML Style Buttons With Org Mode
Thanks for this, will try this for my Emacs config. On Sat, Feb 19, 2022, at 4:51 AM, Juan Manuel Macías wrote: > Juan Manuel Macías writes: > > > If you want to pass the class or id 'manually' to each link, and thus > > have more control, you can evaluate this other version, where the class > > or id would be added at the end of the link description, after (for > > example) "!style": > > PS: Sorry, this is the correct code: > > (org-link-set-parameters "button" >:face '(:foreground "green4" :underline t) >:follow (lambda (path) (browse-url path)) >:export (lambda (path desc backend) > (when (eq backend 'html) >(let ((style (if (string-match "\\(!style\\)\\(.+\\)" desc) > (match-string 2 desc) >"")) > (desc (replace-regexp-in-string "\\(!style .+\\)" "" desc))) > (format "formaction=\"%s\">%s" style >path desc) > > > Example: > > [[button:http://www.sambanya.com/artgallery.html][Art Gallery Page Link > !style class="mybutton"]] > > == HTML ==> > > > formaction="http://www.sambanya.com/artgallery.html";>Art Gallery Page Link > > > >
Re: How to enforce sub-scripts with {} only for HTML export?
Edgar,
one of my .org files has this
# ^:{}: disable super/subscripting: https://stackoverflow.com/a/698791/1527747
#+options: ^:{}
ymmv.
Re: How to enforce sub-scripts with {} only for HTML export?
ed...@openmail.cc writes:
> What am I doing wrong? Thanks!
>
> * Emacs and Org configuration
>
> I am using this with ~emacs -q~:
>
> #+begin_src emacs-lisp
> (setq
> ;; Use {} for super and subscripts
> org-export-with-sub-superscripts "{}")
> #+end_src
{} should be a symbol. Try
(setq org-export-with-sub-superscripts '{})
How to enforce sub-scripts with {} only for HTML export?
Hi. I hope that this is not a known issue and that you can help me.
* Short description
If I export this as html
#+begin_src org
test_my_subs
#+end_src
the corresponding line is exported as
#+begin_src html
testmysubs
#+end_src
* Expected output
I was expecting the output to be
#+begin_src html
test_my_subs
#+end_src
In the [[help:org-export-with-sub-superscripts][documentation]], it
reads:
#+begin_quote
Still, ambiguity is possible. So when in doubt, use {} to enclose
the sub/superscript. If you set this variable to the symbol ‘{}’,
the braces are *required* in order to trigger interpretations as
sub/superscript. This can be helpful in documents that need "_"
frequently in plain text.
#+end_src
What am I doing wrong? Thanks!
* Emacs and Org configuration
I am using this with ~emacs -q~:
#+begin_src emacs-lisp
(setq
;; Use {} for super and subscripts
org-export-with-sub-superscripts "{}")
#+end_src
#+begin_src emacs-lisp
(emacs-version)
#+end_src
#+RESULTS:
: GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27,
cairo version 1.17.4)
: of 2021-03-26
#+begin_src emacs-lisp
(org-version)
#+end_src
#+RESULTS:
: 9.4.6
-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
Re: ox-taskjuggler missing
I used ox-taskjuggler 2 years ago I think, but I remember having to fix some time translation calculation in order to make it work correctly. I have this ox file on my computer and if you are interested I can share it or at least try to run it on my machine if you give me few days. Taskjuggler is an amazing piece of software, and using it with org-mode is really a great combination! Best regards, -- Antonio Carlos PADOAN JUNIOR Phone: +33(0)6 5035 1196 GPG fingerprint: 243F 237F 2DD3 4DCA 4EA3 1341 2481 90F9 B421 A6C9
Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
Ihor, > Which is perfectly fine. 24:29 is one of the expected time formats for > org-agenda. If I recall correctly, this kind of time range is used in > the wild. See https://orgmode.org/list/874l3w7woq@gmail.com ah, i see. thanks for the correction! cheers, Greg
Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
Greg Minshall writes: > i tried Liutos' example, and ended up with > >> * a simple entry >> SCHEDULED: <2022-02-20 Sun 23:59-24:29> > > i think it is the "-24:29" that is of concern. Which is perfectly fine. 24:29 is one of the expected time formats for org-agenda. If I recall correctly, this kind of time range is used in the wild. See https://orgmode.org/list/874l3w7woq@gmail.com Best, Ihor
Re: LaTeX letters in Org
FYI, there's also an article on using the scrlttr2 class from KOMA-script (mostly for European/German usage I guess) for letters: https://orgmode.org/worg/exporters/koma-letter-export.html On Sat, 2022-01-29 at 12:39 -0500, William Denton wrote: > I wrote up how to use Org to write letters with the LaTeX letter class. > Here's the link in case anyone's interested: > > https://www.miskatonic.org/2022/01/28/latex-letters-in-org/ > > Cheers, > > Bill > > -- > William Denton > https://www.miskatonic.org/ > Librarian, artist and licensed private investigator. > Toronto, Canada > signature.asc Description: This is a digitally signed message part
Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
Ihor, i tried Liutos' example, and ended up with > * a simple entry > SCHEDULED: <2022-02-20 Sun 23:59-24:29> i think it is the "-24:29" that is of concern.
