Hello Eric,
On 2020-06-15 10:20, Eric S Fraga writes:
> On Saturday, 13 Jun 2020 at 17:02, Alan Schmitt wrote:
>> This is the crux of the issue: there does not seem to be any way to
>> generate a multi-line header. And this causes problems with LaTeX.
>
> Is the problem solvable in LaTeX? Does
Kyle Meyer writes:
> Stig Brautaset writes:
>
>> For me a2 and a4 returns the same, but a1 and a3 just returns TODO h2.
>> However, I can reproduce what you're seeing by setting this:
>>
>> (setq org-agenda-todo-ignore-scheduled nil)
>
> So, provided you've configured
On Tuesday, 16 Jun 2020 at 10:46, Alan Schmitt wrote:
> You're right, it should work in a single line. I don't what I did that
> made it fail, and I no longer can reproduce it. Sorry for the noise.
Glad you solved it!
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-636-gaa32f6
Hello.
I found that if I do "C-c C-c" on heading, it suggests only local tags in
the minibuffer, but when I do "C-m / m" (build sparse tree) it suggests
agenda tags together with local tags.
It does not make sense to build sparse tree in buffer using tags that are
not in this buffer, I think. So
Thanks for the useful example. I will take a look. Didn't know about org-sbe!
-s-
On Mon, 15 Jun 2020 15:52:16 -0400
Douglas Perrin wrote:
> Hi Salomon Turgman,
> I do this a lot and have had success using a combination of #+SETUPFILE to
> bring in names and configuration, and org-sbe to do
Hello,
Mario Frasca writes:
> how do I run tests from the command line (I'm using make test) but
> then limited to one lisp file? or one specific test?
Use BTEST_RE="regexp" prefix, e.g.,
BTEST_RE="table" make test
Regards,
--
Nicolas Goaziou
Dominik Schrempf writes:
> Hello,
>
> are you looking for, e.g.,
>
> #+latex_header: \addbibresource{bibliography.bib}
> #+latex_header_extra: do some stuff
> #+latex_header_extra: and even more
>
> I don't use the EXPORT keyword at the beginning, I am not sure if it is
> needed.
>
> Best,
>
Hello,
Mario Frasca writes:
> I had a closer look at my changes, re-read it, and used it a bit, and
> I think this is o.k.
It looks fine, indeed.
> see it yourself, when we have the agreement allowing you accept
> changes longer than 15 lines, I'll consider the needed refactoring and
>
On 16/06/2020 11:56, Nicolas Goaziou wrote:
what about waiting until bureaucracy
is over?
I'm fine with it, but I'm accumulating several adjustments, and it's
being difficult to keep track of each of them separately.
Of course, this assumes you're planning to sign FSF papers.
I have
Is it possible to have source code SQL blocks that are processed with a custom
command line tool?
e.g. how can I make something like this to work:
#+begin_src sql :cmdline "osqueryi --json"
select * from processes limit 5;
#+end_src
For those who don't know what osquery is, here's a quote
* It is customary for compilers to avoid claiming authorship over target
code. However, the org-mode publish document publisher silently
inserted licensed content into target documents. This patch replaces
the GPL-V3 licensed highlighter script with a public domain version to
resolve this issue.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ag Ibragimov writes:
> Is it possible to have source code SQL blocks that are processed with a
> custom command line tool?
> e.g. how can I make something like this to work:
>
> #+begin_src sql :cmdline "osqueryi --json"
> select * from
12 matches
Mail list logo
