Hi,
This package
https://github.com/grettke/org-utf-to-xetex
makes it easy to use Emoticons and other Non-Latin characters with XeTeX.
"It works fine on my box."
There is probably a lot of room for improvement, so, please share feedback.
Does something like this already exist?
Sincerely,
On Wed, Jun 27, 2018 at 9:28 AM, Nicolas Goaziou wrote:
> Grant Rettke writes:
>> From: Grant Rettke
>> +;; provides the 'includegraphics' command to tell LaTeX where to find
>> +;; the logo. 'includegraphics' needs to know the logo's directory and
>
> I added two spaces after the periods.
Dear helpful list,
I'm experimenting with an org-agenda setup where I have a directory for
each project, and a README.org with the project TODOs in each directory.
I'm using the elisp below:
#+BEGIN_SRC: emacs-lisp
(setq org-agenda-file-regexp "\\`README\\.org\\'")
(setq
On 28/06/2018 14:53, Uwe Brauer wrote:
> Hi
>
> Org-aggregate is great and very helpful.
>
> However I have some problems/questions which I think a maybe interesting
> for the list.
>
> Take the following code
>
>
> #+begin_src emacs-lisp
> (setq org-calc-default-modes '(calc-internal-prec 12
Hello,
Colin Baxter writes:
> I do not want any output fields of the tables generated by org-collector
> to show double quotes ("). To achieve this, I changed the stringformat
> variable at line 136 of org-collector.el to
>
> (setq stringformat (if noquote "%s" "%s"))
>
> Is there a more
Hello,
I do not want any output fields of the tables generated by org-collector
to show double quotes ("). To achieve this, I changed the stringformat
variable at line 136 of org-collector.el to
(setq stringformat (if noquote "%s" "%s"))
Is there a more elegant way to do this other than my
> "Nicolas" == Nicolas Goaziou writes:
Nicolas> Hello, Colin Baxter writes:
>> I do not want any output fields of the tables generated by
>> org-collector to show double quotes ("). To achieve this, I
>> changed the stringformat variable at line 136 of org-collector.el
Hi
Org-aggregate is great and very helpful.
However I have some problems/questions which I think a maybe interesting
for the list.
Take the following code
#+begin_src emacs-lisp
(setq org-calc-default-modes '(calc-internal-prec 12 calc-float-format
(fix 3);;; the
Hello,
Allen Li writes:
> Running (org-parse-time-string "<@@@>") results in hitting max-lisp-eval-depth
>
> org-parse-time-string calls org-matcher-time calls org-2ft calls
> org-parse-time-string
>
> There is a condition-case in org-2ft that catches the error and
> returns 0, but it would be
