[FEATURE request] hope `org-agenda-custom-commands` can support propertiezed-text.
I want to display text icon using "all-the-icons" package to beautify
org-mode commands interface.
In `org-capture-templates`, I can set description text with propertied text
like this:
```elisp
(setq org-capture-templates
`(("c" ,(format "%s\tsticky note" (all-the-icons-faicon
"sticky-note-o" :face 'all-the-icons-green :v-adjust 0.01))
entry (file "")
;; select todo keyword interactively from `org-todo-keywords'.
;; The `org-todo-keywords-for-agenda' variable is fullfilled with
value AFTER generated Agenda.
"* %(completing-read \"Todo keyword: \"
org-todo-keywords-for-agenda nil t) %^{Capture} [/] \n:PROPERTIES:\n:TIME:
%U\n:END: \n%i\n%a\n\n%?\n"
;; :time-prompt t
:empty-lines 1 :jump-to-captured t))
```
But I can't do similar in `org-agenda-custom-commands` description part
like this:
```elisp
(add-to-list
'org-agenda-custom-commands
'("c" (format "%s Today [c]locked tasks." (all-the-icons-faicon
"hourglass-start"))
((agenda ""
((org-agenda-ndays 1)
(org-agenda-span-1)
(org-agenda-use-time-grid t)
(org-agenda-include-diary nil)
(org-agenda-show-log (quote clockcheck))
(org-agenda-clockreport t))
```
This upper code will report error.
[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
Re: how to add special glyphs
On 3/6/23 16:06, Thomas S. Dye wrote:
Rob Sargent writes:
On 3/6/23 10:42, Rob Sargent wrote:
I settled for \ding{54}, but of course that doesn't work in the HTML
export. I
keep bumping in to this works-here-not-there in export. Quite
disappointing.
LaTeX is great, but not for the faint of heart.
I know two ways that might fix things for you.
One is org-entities-user, which makes a dictionary to cover html and
LaTeX export, e.g.,
(add-to-list 'org-entities-user '("eng" "\\ng" nil "" "g"
"g" "ŋ"))
Another is to use UTF-8 in LaTeX. Here's one of my setups:
#+name: koma-article-liberation
#+header: :results silent
#+begin_src emacs-lisp
(require 'ox-latex)
(add-to-list
'org-latex-classes
'("koma-article-liberation"
"\\documentclass{scrartcl}
[NO-DEFAULT-PACKAGES]
[PACKAGES]
[EXTRA]
\\usepackage{microtype}
\\usepackage{amstext}
\\usepackage{fontspec}
\\usepackage{unicode-math}
\\defaultfontfeatures{Ligatures=TeX}
\\setmainfont{Liberation Serif}
\\setsansfont{Liberation Sans}[Scale=MatchLowercase]
\\setmonofont{Liberation Mono}[Scale=MatchLowercase]
\\usepackage{paralist}
\\let\\itemize\\compactitem
\\let\\description\\compactdesc
\\renewenvironment{enumerate}{\\begin{inparaenum}[(i)]}{\\end{inparaenum}}
\\usepackage{fewerfloatpages}
\\usepackage{graphicx}
\\usepackage{textcomp}
\\usepackage{array}
\\usepackage[x11names]{xcolor}
\\usepackage[colorlinks=true,allcolors=Blue4]{hyperref}
\\usepackage[color=blue]{attachfile2}
\\usepackage[cache=false]{minted}
\\usemintedstyle{tango}
\\usepackage{rotating}
\\usepackage[authordate, giveninits=true, noibid, sortcites=true,
backend=biber, bibencoding=utf8]{biblatex-chicago}
\\addbibresource{tsd.bib}
\\newcommand{\\rc}{$^{14}$C}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
#+end_src
The key here is the fontspec package.
If you go the UTF-8 route, then you'll need to compile with either
XeLaTeX or LuaLaTeX, something like this:
#+name: xelatex-biber
#+header: :results silent
#+begin_src emacs-lisp
(setq org-latex-pdf-process
'("xelatex -interaction nonstopmode -shell-escape
-output-directory %o %f"
"biber %b"
"xelatex -interaction nonstopmode -shell-escape
-output-directory %o %f"
"xelatex -interaction nonstopmode -shell-escape
-output-directory %o %f"))
#+end_src
hth,
Tom
Thanks again.
I think I have to decide on one format and stick with it. I get bitten
by ODT/DOC transformations, not sure I like the default look of
LaTeX/pdf, HTML is pretty reliable but not best for handing out. Maybe
I'll go back to "text" and call it good.
Cheers,
rjs
Re: how to add special glyphs
Rob Sargent writes:
On 3/6/23 10:42, Rob Sargent wrote:
I settled for \ding{54}, but of course that doesn't work in the
HTML export. I
keep bumping in to this works-here-not-there in export. Quite
disappointing.
LaTeX is great, but not for the faint of heart.
I know two ways that might fix things for you.
One is org-entities-user, which makes a dictionary to cover html
and LaTeX export, e.g.,
(add-to-list 'org-entities-user '("eng" "\\ng" nil "" "g"
"g" "ŋ"))
Another is to use UTF-8 in LaTeX. Here's one of my setups:
#+name: koma-article-liberation
#+header: :results silent
#+begin_src emacs-lisp
(require 'ox-latex)
(add-to-list
'org-latex-classes
'("koma-article-liberation"
"\\documentclass{scrartcl}
[NO-DEFAULT-PACKAGES]
[PACKAGES]
[EXTRA]
\\usepackage{microtype}
\\usepackage{amstext}
\\usepackage{fontspec}
\\usepackage{unicode-math}
\\defaultfontfeatures{Ligatures=TeX}
\\setmainfont{Liberation Serif}
\\setsansfont{Liberation Sans}[Scale=MatchLowercase]
\\setmonofont{Liberation Mono}[Scale=MatchLowercase]
\\usepackage{paralist}
\\let\\itemize\\compactitem
\\let\\description\\compactdesc
\\renewenvironment{enumerate}{\\begin{inparaenum}[(i)]}{\\end{inparaenum}}
\\usepackage{fewerfloatpages}
\\usepackage{graphicx}
\\usepackage{textcomp}
\\usepackage{array}
\\usepackage[x11names]{xcolor}
\\usepackage[colorlinks=true,allcolors=Blue4]{hyperref}
\\usepackage[color=blue]{attachfile2}
\\usepackage[cache=false]{minted}
\\usemintedstyle{tango}
\\usepackage{rotating}
\\usepackage[authordate, giveninits=true, noibid,
sortcites=true, backend=biber,
bibencoding=utf8]{biblatex-chicago}
\\addbibresource{tsd.bib}
\\newcommand{\\rc}{$^{14}$C}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
#+end_src
The key here is the fontspec package.
If you go the UTF-8 route, then you'll need to compile with either
XeLaTeX or LuaLaTeX, something like this:
#+name: xelatex-biber
#+header: :results silent
#+begin_src emacs-lisp
(setq org-latex-pdf-process
'("xelatex -interaction nonstopmode -shell-escape
-output-directory %o %f"
"biber %b"
"xelatex -interaction nonstopmode -shell-escape
-output-directory %o %f"
"xelatex -interaction nonstopmode -shell-escape
-output-directory %o %f"))
#+end_src
hth,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
Re: how to add special glyphs
On 3/6/23 10:42, Rob Sargent wrote:
On 3/6/23 10:37, Thomas S. Dye wrote:
Rob Sargent writes:
I have added a "boxed x" and "CHECK MARK" to my document, but they
do not get exported to pdf output. They are in the .tex file, and do
go through to the HTML. So far I'm using these
packages
#+LaTeX_HEADER: \usepackage[T1]{fontenc}
#+LaTeX_HEADER: \usepackage{libertine}
#+LaTeX_HEADER: \usepackage[margin=0.80in]{geometry}
#+LaTeX_HEADER: \usepackage{setspace}
#+LaTeX_HEADER: \usepackage{enumitem}
#+LaTeX_HEADER: \usepackage{endnotes}
(Bonus points for UTF8 code for the opposite of "CHECK MARK"?)
You need a package like wasysym that defines these symbols. Check the
web for David Carlisle, Scott Pakin, and Alexander Holt's "The Great,
Big List of LaTeX Symbols" for more information.
All the best,
Tom
I settled for \ding{54}, but of course that doesn't work in the HTML
export. I keep bumping in to this works-here-not-there in export. Quite
disappointing.
Re: how to add special glyphs
On 3/6/23 10:37, Thomas S. Dye wrote:
Rob Sargent writes:
I have added a "boxed x" and "CHECK MARK" to my document, but they do
not get exported to pdf output. They are in the .tex file, and do go
through to the HTML. So far I'm using these
packages
#+LaTeX_HEADER: \usepackage[T1]{fontenc}
#+LaTeX_HEADER: \usepackage{libertine}
#+LaTeX_HEADER: \usepackage[margin=0.80in]{geometry}
#+LaTeX_HEADER: \usepackage{setspace}
#+LaTeX_HEADER: \usepackage{enumitem}
#+LaTeX_HEADER: \usepackage{endnotes}
(Bonus points for UTF8 code for the opposite of "CHECK MARK"?)
You need a package like wasysym that defines these symbols. Check the
web for David Carlisle, Scott Pakin, and Alexander Holt's "The Great,
Big List of LaTeX Symbols" for more information.
All the best,
Tom
Thank you,
rjs
PS I think the list got your answer twice?
Re: how to add special glyphs
Rob Sargent writes:
I have added a "boxed x" and "CHECK MARK" to my document, but
they do not get exported to pdf output. They are in the .tex
file, and do go through to the HTML. So far I'm using these
packages
#+LaTeX_HEADER: \usepackage[T1]{fontenc}
#+LaTeX_HEADER: \usepackage{libertine}
#+LaTeX_HEADER: \usepackage[margin=0.80in]{geometry}
#+LaTeX_HEADER: \usepackage{setspace}
#+LaTeX_HEADER: \usepackage{enumitem}
#+LaTeX_HEADER: \usepackage{endnotes}
(Bonus points for UTF8 code for the opposite of "CHECK MARK"?)
You need a package like wasysym that defines these symbols. Check
the web for David Carlisle, Scott Pakin, and Alexander Holt's "The
Great, Big List of LaTeX Symbols" for more information.
All the best,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
Re: visual-line-mode don't play well with org-latex-preview
On Thursday, 2 March 2023 20:00:14 CET Bruno Barbier wrote:
>
> Hi Chris,
>
> chris writes:
>
> > Hi all,
> >
> > ```
> > hello hello hello hello hello hello hello hello hello hello hello hello
> > hello
> > hello hello \(\text {hello hello hello hello hello hello hello hello}\)
> > ```
> >
> > If you put the above text in a org file, and activate `visual-line-mode`
> > and
> > `org-latex-preview`, depending on the length of the initial part of the
> > text,
> > the generated png/svg image from latex expression can be displayed in full,
> > partially hidden or totally hidden.
> >
>
> I'm observing the same behavior.
>
> The preview is not always fully visible. But, after adding some text
> (at least one space after the preview), Emacs wraps as needed, so that
> the preview remains visible.
That is a very nice workaround.
> Emacs is just not wrapping correctly in
> that edge case, where there is nothing at all after the latex preview.
>
> The behavior looks the same using only text-mode (without using org).
> You should probably report this as an Emacs bug (see M-x
> report-emacs-bug).
What command for latex preview in text mode? (I'll probably figure that out.)
Yes, I should definitely report that bug.
Thanks a lot,
Chris
>
> Bruno
>
how to add special glyphs
I have added a "boxed x" and "CHECK MARK" to my document, but they do
not get exported to pdf output. They are in the .tex file, and do go
through to the HTML. So far I'm using these packages
#+LaTeX_HEADER: \usepackage[T1]{fontenc}
#+LaTeX_HEADER: \usepackage{libertine}
#+LaTeX_HEADER: \usepackage[margin=0.80in]{geometry}
#+LaTeX_HEADER: \usepackage{setspace}
#+LaTeX_HEADER: \usepackage{enumitem}
#+LaTeX_HEADER: \usepackage{endnotes}
(Bonus points for UTF8 code for the opposite of "CHECK MARK"?)
Re: [PATCH] org-src: Improve the name of source editing buffers
On 06/03/2023 04:26, Rudolf Adamkovič wrote: -Format is \"*Org Src ORG-BUFFER-NAME [ LANG ]*\"." - (concat "*Org Src " org-buffer-name "[ " lang " ]*")) +Format is \"*Org Src ORG-BUFFER-NAME [LANG]*\"." + (concat "*Org Src " org-buffer-name " [" lang "]*")) May it be a breaking change for users having customized `display-buffer-alist'? Should it be advertised in ORG-NEWS? I am not sure though.
Re: [BUG] No space after footnote with org-export-with-footnotes set to nil [9.6.1 ( @ /Users/test/.emacs.d/elpa/28.0/develop/org-9.6.1/)]
On 05/03/2023 20:01, Ihor Radchenko wrote: Consider * Heading [0/1] text ... Text with newline\\ [footnote] more text. ... Text (parens[footnote] ). I am not convinced that space should be dropped here. It might be enough to use spaces if and only if there are no preceding spaces. Or not. One may think of other edge cases. An idea: retain :post-blank having more spaces. Newline > tab, tab = 8 spaces. Ihor, could you, please, be more specific concerning languages where spaces may be used before footnote marks? I would expect at least non-breakable spaces, but they are not stripped currently.
Re: [PATCH] Fix LaTeX misspelled as Latex
On 06/03/2023 04:04, Rudolf Adamkovič wrote: (1) a unified commit message with the similar BibTeX patch, and * lisp/org-element.el: Spell LaTeX correctly. * lisp/ox-ascii.el: Spell LaTeX correctly. * lisp/ox-html.el: Spell LaTeX correctly. Accordingly to the CONTRIBUTE file in the Emacs repository there is no need to repeat the same message: * lisp/window.el (handle-select-window): * src/frame.c (Fhandle_switch_frame, Fselected_frame): Deactivate the mark.
Re: [FR] ob-awk.el specifying a delimeter argument in for output
On 05/03/2023 16:50, Jeremie Juste wrote:
#+begin_src awk :in-file test.csv :cmd-line -F ","
{print $0}
#+end_src
Notice that awk has Output Field Separator that is space by default and
may be set using -v OFS=; (or --assign) command line options. -F option
sets input field separator FS variable.
"print $0" just sends input record to output literally. If you try to
modify some field then record is rebuilt taken into account OFS
echo 1,2 | awk -F , '{ $1=$1+10; print; }'
11 2
See (info "(awk) Changing Fields)")
https://www.gnu.org/software/gawk/manual/gawk.html#Changing-Fields
I just have found this link on stackoverflow. It is enough to add even
$1=$1 that should not really modify field values.
So I expect less issues with a more realistic example.
As to ";" as CSV values separator, it often appears with "," as decimal
separator 1234,56 and dd.mm. date formats. Unfortunately handling of
localized data formats is not a strong side of Emacs. E.g. fixed
LC_NUMERIC=C forces "." as decimal separator, date parsing functions are
rather limited.
