Hi,
On Fri, Feb 2, 2018 at 10:24 AM, numbch...@gmail.com
wrote:
> When I try to compile with command `make`, but got this output:
[...]
> make -C lisp compile
just do `make compile`.
you can't use `-C` in org-mode source tree.
In my case with `-C`, I get:
$ make -C lisp
Hi,
On Thu, Feb 1, 2018 at 11:55 PM, Nicolas Goaziou wrote:
> Yasushi SHOJI writes:
>
>> What if _I_, for my own project, want to customize the formatter and like to
>> call fill-paragraph, can I still do this?
>
> No need to tweak the formatter.
When I enable `eldoc-mode` in org-mode.
eldoc timer running when on `shell` src blocks like:
#+begin_src shell
git log $rev..origin/emacs-25 -- lisp/org doc/misc/org.texi \
etc/refcards/orgcard.tex etc/ORG-NEWS etc/org \
etc/schema/od-manifest-schema-v1.2-os.rnc \
When I try to compile with command `make`, but got this output:
```
make -C doc clean; make -C lisp clean;
make[1]: Entering directory '/home/stardiviner/Code/Emacs/org-mode/doc'
rm -f org *.pdf *.html *_letter.tex org-version.inc org-version.tex \
*.aux *.cp *.cps *.dvi *.fn *.fns *.ky
Hi,
On Thu, Feb 1, 2018 at 9:29 PM, Alan Schmitt
wrote:
> Not here. If I try to export the second file (the one with the link to
> the first file), I get an error:
>
> user-error: Unable to resolve link: "*A headline"
I now see that I totally misread your
Hello,
Jose Robins writes:
> I'm in the pacific time zone, and I've set the org-clock-mode-line-total to
> today. The modeline display that shows the current time for today seems to
> consider 'today' as UTC midnight to UTC midnight and does not respect my
> timezone. I
org-clock.el: Add an autoload entry for the function org-clock-sum-today
* lisp/org-clock.el: When the org-mode is called for the very first time
any functionality that requires the org-clock-sum-today used to fail.
(e.g. a column that calculates CLOCKSUM_T)
Jose
Hello,
John Kitchin writes:
> I use results drawers for my src blocks alot, and for a while now every
> time I run one block, it folds all the other results drawers, unless I use
> visible-mode.
>
> Is there a way to prevent this drawer folding so that they are open
I use results drawers for my src blocks alot, and for a while now every
time I run one block, it folds all the other results drawers, unless I use
visible-mode.
Is there a way to prevent this drawer folding so that they are open when I
open a document, and they stay open while running blocks?
So a left-to-right listing of (colon-separated) tags after the heading
cannot imply a higher-to-lower hierarchical order? So there is no hierarchy
unless you create it, e.g.,
(setq org-tag-alist '((:startgrouptag)
("GTD")
(:grouptags)
On 2018-01-26, at 19:41, Nick Dokos wrote:
> Marcin Borkowski writes:
>
>> Hi all,
>>
>> I want to be able to dynamically switch between various settings of
>> org-clock-mode-line-total. To this end, I wrote the following code.
>>
>> (setq
Luis Roca wrote:
> Installing ox-rst returns the following error in *Messages*:
>
>`Incompatible because it depends on uninstallable packages.`
>
> Reviewing other Org export packages reveals the same note for each.
I would guess this is because Org is not recognized as a built-in
I'm in the pacific time zone, and I've set the org-clock-mode-line-total to
today. The modeline display that shows the current time for today seems to
consider 'today' as UTC midnight to UTC midnight and does not respect my
timezone. I have to set the org-extend-today-until variable to 8 (PST-UTC
On Thu, Feb 1, 2018 at 10:30 AM John Kitchin
wrote:
> I was not aware of any implied hierarchy with tags. The order is not
> important as far as I know, and what you describe as mix-and-match seems
> ok. There is an idea of inheritance, e.g. sub-headings can inherit tags
I was not aware of any implied hierarchy with tags. The order is not
important as far as I know, and what you describe as mix-and-match seems
ok. There is an idea of inheritance, e.g. sub-headings can inherit tags
from higher headings.
In any case, you should be able to use agenda queries to find
Is it possible to have two or more tags that are "peers," i.e., all equal,
not in a hierarchy, be in an ad-hoc, as-needed way be hierarchical? For
example, I have the tags *org-mode, lisp, *and *emacs, *and I want to have
a header with the tags
* my header:emacs:org-mode:lisp:
So the above
Hello,
Yasushi SHOJI writes:
> What if _I_, for my own project, want to customize the formatter and like to
> call fill-paragraph, can I still do this?
No need to tweak the formatter. You can post-process its output to your
liking, e.g., with `org-fill-paragraph'
Nicolas Goaziou writes:
>> When depth is -1, wholenump form evaluates to nil, and setcounter
>> command is not exported at all.
>
> I don't think it's a bug. Org doesn't pretend to support every LaTeX
> feature. Setting `org-export-with-toc', which is where DEPTH comes
On 2018-02-01 13:56, Nicolas Goaziou writes:
>> Not here. If I try to export the second file (the one with the link to
>> the first file), I get an error:
>>
>> user-error: Unable to resolve link: "*A headline"
>>
>> This is why I think I need to have the target file name
On 2018-02-01 13:02, Nicolas Goaziou writes:
>> My use case is this one: I have a link to a custom id, and I want to
>> export it as [[#id]] in latex and [[file:file.org::#id]] for html
>> *before* link resolution happens (so that the custom id in the latex
>> export is
Hello,
Alan Schmitt writes:
> On 2018-02-01 20:09, Yasushi SHOJI writes:
>
>>> How do I change the link in the second headline so that I can split the
>>> second headline into its own file and export it by itself?
>>
>> Using [[*A
On 2018-02-01 20:09, Yasushi SHOJI writes:
>> How do I change the link in the second headline so that I can split the
>> second headline into its own file and export it by itself?
>
> Using [[*A headline]] ?
>
> I might be still missing something but I got following:
>
>
On Thu, Feb 1, 2018 at 8:43 PM, Yasushi SHOJI wrote:
> On Mon, Jan 29, 2018 at 11:41 PM, Nicolas Goaziou
> wrote:
>> Yasushi SHOJI writes:
>>
>>> Do you see this on your env? Or, is it just me?
>>
>> I don't see anything
Hello,
Alan Schmitt writes:
> Is there a way to define a macro that has different behaviors depending
> on export backend? I have macros that use the @@latex:foo@@ syntax, but
> in that case I "foo" is supposed to be literal latex.
>
> My use case is this one: I
Hi,
On Mon, Jan 29, 2018 at 11:41 PM, Nicolas Goaziou
wrote:
> Yasushi SHOJI writes:
>
>> Do you see this on your env? Or, is it just me?
>
> I don't see anything like this.
Hmm... I don't know how to fix this.
>> I'd like to have the
Hi,
On Thu, Feb 1, 2018 at 5:45 PM, Alan Schmitt
wrote:
> On 2018-02-01 11:17, Yasushi SHOJI writes:
>> On Fri, Jan 26, 2018 at 2:37 AM, Alan Schmitt
>> wrote:
>>> My question is about pdf export. Is it
Hello,
Is there a way to define a macro that has different behaviors depending
on export backend? I have macros that use the @@latex:foo@@ syntax, but
in that case I "foo" is supposed to be literal latex.
My use case is this one: I have a link to a custom id, and I want to
export it as [[#id]]
On 2018-02-01 11:17, Yasushi SHOJI writes:
> On Fri, Jan 26, 2018 at 2:37 AM, Alan Schmitt
> wrote:
>> I'm working on a project that is becoming too big to manage as a single
>> file, so I'm looking at splitting it in several files. This
28 matches
Mail list logo