Thanks for an answer, in any place first :).
Am Di., 6. Apr. 2021 um 05:46 Uhr schrieb Kyle Meyer :
> [ Sorry for the slow reply. ]
>
> Simon Braß writes:
>
> > Hi all,
> >
> > I've tried to open an attached file (added with org-attach-attach),
> however,
> > when I try to open it with C-c C-o I
[ Sorry for the slow reply. ]
Simon Braß writes:
> Hi all,
>
> I've tried to open an attached file (added with org-attach-attach), however,
> when I try to open it with C-c C-o I got the following backtrace:
>
> #+begin_example
> Debugger entered--Lisp error: (wrong-number-of-arguments (2 . 2) 1)
autofrettage writes:
> I recently read about the #+STARTUP parameter "hideblocks", but it
> doesn't seem to have any effect in my set-up. All the blocks kept
> laughing straight in my face. :-(
>
> Any ideas about what could have gone wrong?
Are you leaving org-startup-folded at showeverything (t
Ingo Lohmar writes:
> I stumbled upon weird behavior when using `org-toggle-link-display', and
> I finally checked what that is about.
>
> Observation:
> - use `org-toggle-link-display' in org buffer A, and (coming
> from the defaults) links are now shown in full (not just the
> description),
Kyle,
> The below change seems to fix the issue, though Nicolas may be able to
> suggest a more appropriate change.
yes, that seems to work for me.
cheers, Greg
> diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
> index 932f38530..ac24f1f74 100644
> --- a/lisp/ox-latex.el
> +++ b/lisp/ox-la
[ Sorry for the slow response. ]
Adam Sneller writes:
> I have a function that searches for broken fuzzy links in org-mode and
> applies org-warning face to anything it finds:
>
> (org-link-set-parameters
> "fuzzy"
> :face (lambda (path)
> (let ((org-link-search-inhibit-query t))
> (if (condition
Greg Minshall writes:
> hi. running c881b60593b3beeed7b8c7a2bada64157cd9940a, the following
>
>
> *** this =equals= that
>
> and, so on
>
>
> exporting [C-e l o], gives
> : replace-regexp-in-string: Wrong type argument: arrayp, nil
Thanks for reporting. The failure was introduced by
Hi Arne,
Dr. Arne Babenhauserheide writes:
> Except if there is any feature you want to use that doesn’t work under
> LuaTeX.
>
> pdfpages for example says that it only supports pdflatex and vtex.
pdfpages works perfectly with both LuaTeX and XeTeX. I've been using it
in LuaLaTeX for quite some
Juan Manuel Macías writes:
> would dare to say the following: unless you want to maintain some
> backward compatibility with old documents, I highly recommend using
> LuaTeX or XeTeX, especially LuaTeX. Although pdfTeX is very popular
> among average or veterans LaTeX users, I think using it nowa
Hi all,
There have been some threads recently about exporting to LaTeX, but I
think something that I consider interesting for novice Org/LaTeX users
has not been commented: the choice of the TeX engine. I think this is
important because although people often say they "use LaTeX", what they
actuall
The following MWE illustrates:
--8<---cut here---start->8---
#+COLUMNS: %25ITEM %6CLOCKSUM{:}
* Goal 3
:PROPERTIES:
:ID: goal_3
:END:
#+BEGIN: columnview :hlines 4 :id goal_3 :maxlevel 3
#+END
** TODO Task 1
:LOGBOOK:
CLOCK: [2020-01-26 18:05
hi. running c881b60593b3beeed7b8c7a2bada64157cd9940a, the following
*** this =equals= that
and, so on
exporting [C-e l o], gives
: replace-regexp-in-string: Wrong type argument: arrayp, nil
cheers, Greg
=
backtrace:
Debugger entered--Lisp error: (wrong-type-argument arrayp
Hi all,
I am a fanatic Helm user, and within Helm I make intensive use of
helm-surfraw. It is necessary to install Surfraw on the system (in Arch
it is in the community repository). For who does not know, Surfraw
(https://en.wikipedia.org/wiki/Surfraw) is a script written by Julian
Assange that le
Missed removing a debug message. Here is the correct patch. Best,
Tom
On Sun, Apr 4, 2021 at 10:22 PM Tom Gillespie wrote:
>
> Hi Nicolas,
>I've attached a patch with a first pass implementation that I think
> resolves most of the issues. It probably needs a few tests to go along
> with it, b
14 matches
Mail list logo
