Hello,
Bernt Hansen writes:
>Notice modeline total has [0:05/0:15]
>So 'do something' has an effort of 15 minutes. It may be entered wrong
> but it is a bare 15 value
>instead of 15:00 or 00:15
>
>:EFFORT: 15
>
> 6) Go back to Test Parent
>C-c C-p
>
> 7)
Hi,
There seems to be an issue with inherited tag alignment in block agendas
in the master branch.
ECM follows.
Thanks,
Bernt
-- test.el
--
(setq org-agenda-custom-commands
(quote ((" " "Agenda"
Hi,
I noticed maint (and master) has inconsistent handling for effort amounts
Below is an ECM to reproduce the behaviour.
Thanks for Org-Mode!
Regards,
Bernt
--- test.org
-
#+FILETAGS: TEST
#+STARTUP: content
*Keys
Hi,
This bug is mainly a visual annoyance when filtering by tag in the
agenda. It is low priority to fix but I thought I should report it
anyway.
Thanks for all your fabulous work on org-mode!
Regards,
Bernt
--- test.org
Nicolas Goaziou writes:
> Hello,
>
> Bernt Hansen writes:
>
>> I updated to the latest master this morning and my agenda no longer has
>> any tasks in it.
>
> Fixed. Thank you.
>
> Regards,
Confirmed the fix works :) Thanks for the ultra-quick
Hello,
Bernt Hansen writes:
> I updated to the latest master this morning and my agenda no longer has
> any tasks in it.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Hi Aaron,
I updated to the latest master this morning and my agenda no longer has
any tasks in it.
I think this commit breaks my agenda:
commit c9dd7a6a9de34b8094ad6a419260fcc1214cc791 (HEAD)
Author: Aaron Ecay
Date: Thu May 10 01:35:08 2018 +0100
org-agenda:
Tom Purl writes:
> Thank you for your quick response Nicholas. I read that help page but
> I still think this may be a bug. In the 8.2 version of Org the
> Priority column in the column view showed an empty priority if the
> TODO didn't have a priority. Those TODO's where then
‐‐‐ Original Message ‐‐‐
On May 9, 2018 7:32 AM, Nicolas Goaziou wrote:
> Hello,
>
> Tom Purl t...@tompurl.com writes:
>
> > I like to use column view with my org agenda. One of the custom
> >
> > properties that I like to view is the priority. Here's what I
Hello,
Tom Purl writes:
> I like to use column view with my org agenda. One of the custom
> properties that I like to view is the priority. Here's what I do to make
> that happen:
>
> (setq org-agenda-overriding-columns-format "%TODO %4PRIORITY(Pri.)
> %50ITEM(Task)")
I like to use column view with my org agenda. One of the custom
properties that I like to view is the priority. Here's what I do to make
that happen:
(setq org-agenda-overriding-columns-format "%TODO %4PRIORITY(Pri.)
%50ITEM(Task)")
Using Org 8.2 I was able to view the priority in the
Hello,
tumashu writes:
> I found [:alnum:] can match Chinese
>
> (string-match-p "[[:alnum:]]" "@@@你好") => 3
Great.
>
> But using [:word:] may better, in my opinion.
I'm not so sure about it. It would be better to see a concrete
limitation before extending syntax for
Hi,
Xu Chunyang writes:
> By the way, the implementation of ob-python.el is not very robust.
Yes, we need help for this.
--
Bastien
Hi Chunyang,
This bug was introduced by commit 1966d58b2, which “fixed” another
problematic case of indentation. Because of issues like this, ob-python
has never really worked reliably (in my experience)
The only sensible way I can see to evaluate python code from emacs
without hitting these
At 2018-05-07 21:22:34, "Nicolas Goaziou" wrote:
>Hello,
>
>tumashu writes:
>
>> 1. [:alnum:] can not match Chinese char, what about add [:multibyte:] ?
>
>What about :
>
> [:alnum:] + [:multibyte:] -> [:word:]
I found [:alnum:] can match
>
>Could you test this change?
Seem to work!
Another problem I have found is that: when having Chinese char,
(window-text-width) is not a stable method, but I do
not know how to fix it.
```
(defun org-agenda-align-tags ( line)
"Align all tags in agenda items to `org-agenda-tags-column'."
Hello,
tumashu writes:
> 1. [:alnum:] can not match Chinese char, what about add [:multibyte:] ?
What about :
[:alnum:] + [:multibyte:] -> [:word:]
Could you test this change?
Regards,
--
Nicolas Goaziou
1. [:alnum:] can not match Chinese char, what about add [:multibyte:] ?
```
(defun org--align-tags-here (to-col)
...
(if (or (not (looking-at ".*?\\([ \t]+\\)\\(:[[:alnum:]_@#%:]+:\\)[
\t]*$"))
...
)
(defun org-agenda-align-tags ( line)
...
(while (re-search-forward "\\([
Execute this code block
#+BEGIN_SRC python :session :results value
def int2str(i):
digits = "0123456789"
if i == 0:
return "0"
else:
result = ""
while i > 0:
result = digits[i % 10] + result
i = i // 10
return
In a simple klipse test by N. Raghavendra (thanks) is at here:
http://www.retrotexts.net/tmp/ox-html-klipse/
It works fine.
But when I add `(org-html-use-infojs t)` into `EMACS=` code's let-binding.
klipse has problem.
Can't find out the bug, because I don't know JavaScript.
Is there someone
Hello,
em...@edgar-kalkowski.de writes:
> Greetings fellow org-mode enthusiasts,
>
> I discovered that in the latest org-mode setting
> (org-archive-subtree-add-inherited-tags t) only includes inherited tags
> but omits local tags.
[...]
> However, I am not sure if this is enough or if
Greetings fellow org-mode enthusiasts,
I discovered that in the latest org-mode setting
(org-archive-subtree-add-inherited-tags t) only includes inherited tags
but omits local tags.
To remedy this I propose the following patch to org-archive.el:
diff --git a/org-archive.el b/org-archive.el
Thanks. I went carefully though my init file (which I should have done
before I submitted the bug), and discovered that this is a change in terms
of how filladapt-mode interacts with org-mode. There's really no reason to
have filladapt on when org is on, so I just disabled it.
Sorry for the
Hello,
Yaron Minsky writes:
> Oddly, it also gets indentation wrong. So if I start with this:
>
> - asdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf
> asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf asdfasdf
> asdfasdf asdfasdf asdfasdf asdfasdf
Nicolas Goaziou wrote:
> Dmitry Alexandrov <321...@gmail.com> writes:
>> with the latest Emacs from git master, exporting #+begin_right block
>> neither to HTML, nor to ODT (didn’t test other options) does not work
>> as expected, while this should be pretty possible with
This problem crops up when I install 9.1.11. I was previously using an
8.* version of org, and didn't see an issue. The basic problem is that
every time I do M-q to fill a paragraph, it deletes an extra line from
right after the paragraph, eventually sucking in following headers and
paragraphs
Nicolas Goaziou wrote:
> Dmitry Alexandrov <321...@gmail.com> writes:
>
>> Now, I am not sure, whether am I supposed to use #+begin_org-center
>> blocks instead of #+begin_center too.
>
> The latter. As I explained, ".org-center" is an internal style.
>
>> In fact, given
Hi Bernt,
Bernt Hansen writes:
>> Fixed. Thank you.
>
> Confirmed. Thanks!!!
Indeed, thanks too!
> I am always amazed at how fast bugs are addressed on this project.
That's because the place we report bugs is also the place we solve
them ;)
--
Bastien
Nicolas Goaziou writes:
> Bastien writes:
>
4) SPC now does not work to insert a space after the TODO so I can type my
headline
I have to use C-f
>>
>> I still have this issue with current master.
>
>
> Fixed. Thank you.
Confirmed.
Hello,
Rainer Stengele writes:
> Please change org-agenda-tags-column to something other than the default, for
> example -160.
> Does the standard agenda ("C-c a a") respect the variable in your case?
> It doesn't seem to in my setting.
Fixed. Thank you.
Regards,
Hello,
Xu Chunyang writes:
> I'm using latest Org mode built from latest git repository, the HEAD
> is 4c13d0a1a870a450627ce1d8449a3b7204202250. I notice tags are no longer
> aligned in *Org Agenda*.
>
> It seems the issue is introduced by
>
>
Hi,
I'm using latest Org mode built from latest git repository, the HEAD
is 4c13d0a1a870a450627ce1d8449a3b7204202250. I notice tags are no longer
aligned in *Org Agenda*.
It seems the issue is introduced by
e87ebca2a755620a13a49cc748ba987b17d2d64d Use `org-tag-line-re'
and the following
Hello,
Bastien writes:
>>> 4) SPC now does not work to insert a space after the TODO so I can type my
>>> headline
>>>I have to use C-f
>
> I still have this issue with current master.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Dmitry Alexandrov <321...@gmail.com> writes:
> Just another unofficial reference card [0], by Caio Rordrigues at that time,
> that again states that:
>
> #+begin_right This text is aligned to the right! #+end_right
>
> These persons are probably consider themselves highly familiar with
> Org,
Dmitry Alexandrov <321...@gmail.com> writes:
> Now, I am not sure, whether am I supposed to use #+begin_org-center
> blocks instead of #+begin_center too.
The latter. As I explained, ".org-center" is an internal style.
> In fact, given that #+begin_center creates a .org-center div block,
> that
Hello,
Dmitry Alexandrov <321...@gmail.com> writes:
> with the latest Emacs from git master, exporting #+begin_right block
> neither to HTML, nor to ODT (didn’t test other options) does not work
> as expected, while this should be pretty possible with both.
>
> With HTML, as far as I can see,
Hi Nicolas,
Nicolas Goaziou writes:
>> 4) SPC now does not work to insert a space after the TODO so I can type my
>> headline
>>I have to use C-f
I still have this issue with current master.
Those lines in `org--align-tags-here' are problematic:
Hi Bernt,
Bernt Hansen writes:
> Hi Bastien! I have been away from this list for far too long -- hoping
> to correct that.
I hope too!
As Org keeps moving forward with rewritten and new functionalities,
it's essential to get tests and feedback from long-time power users.
--
Hello,
Bernt Hansen writes:
> With the below org file tags handling behaves in a surprising way.
>
>
> * TODO Test Parent :PRODUCTION:MISC:
> ** TODO foo :BAR:
> ** keys to
Bastien writes:
> Hi Bernt,
>
> glad to read you!
>
Hi Bastien! I have been away from this list for far too long -- hoping
to correct that.
> Bernt Hansen writes:
>
>> With the below org file tags handling behaves in a surprising way.
>
> Thanks for the report
Hi Bernt,
glad to read you!
Bernt Hansen writes:
> With the below org file tags handling behaves in a surprising way.
Thanks for the report - just a quick check, do you have these
issues on the maint branch as well or just on master?
No problem if you cannot check, just
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hi Adam,
Adam Faryna writes:
> When use org-capture which template that targets file with :prepend
> t, org-capture-kill removes one char too much from target buffer, in
> result next item in target file looses one of asterisk.
Do you still have this issue?
If so, can
Hi Martin,
Martin Kampas writes:
> With headlines like
>
> * [[http://example.com]] Example
>
> org-collector writes just "http://example.com; in the table, omitting the
> rest of the headline.
>
> Patch below.
Applied in maint, thanks!
--
Bastien
Hi Allen Li,
thanks for reporting this. I think both behavior are good
defaults, I tried to enhance the documentation a little bit.
If you see another way to enhance the documentation or the
message sent by org-mode, can you suggest it?
Thanks!
--
Bastien
Hi Xu Chunyang,
Xu Chunyang writes:
> After 'M-x org-tags-view c-g', there is a empty buffer named *Org Agenda*
> left, which is unwanted to me.
Fixed in maint, thanks.
--
Bastien
Hi Allen,
Allen Li writes:
>> https://code.orgmode.org/bzg/org-mode/commit/b9b921716ba1d2a564bb9443427dfb21bb609e05
>> https://code.orgmode.org/bzg/org-mode/commit/da83e7d583895976a2398becbb995bcce1f729be
>
> Oops, done. Attached new patch.
applied in maint, thanks
Hi Xu,
Xu Chunyang writes:
> 'C-h f org-eww-copy-for-org-mode' has the following
>
> and insert the transformed test into the kill ring
>
> "test" should be "text".
Fixed, thanks!
--
Bastien
'C-h f org-eww-copy-for-org-mode' has the following
and insert the transformed test into the kill ring
"test" should be "text".
Am 25.04.2018 um 00:02 schrieb Nicolas Goaziou:
Hello,
Rainer Stengele writes:
running latest Org mode version 9.1.11 (release_9.1.11-620-ga548e4
my agenda views do no more align tags at the set column org-agenda-tags-column.
Tags are added directly after the
Hello,
Rainer Stengele writes:
> running latest Org mode version 9.1.11 (release_9.1.11-620-ga548e4
> my agenda views do no more align tags at the set column
> org-agenda-tags-column.
> Tags are added directly after the agenda item subject.
> I think this has
Hi,
running latest Org mode version 9.1.11 (release_9.1.11-620-ga548e4
my agenda views do no more align tags at the set column org-agenda-tags-column.
Tags are added directly after the agenda item subject.
I think this has recently changed. Did I miss a changed setting or is this a
bug?
Hi,
With headlines like
* [[http://example.com]] Example
org-collector writes just "http://example.com; in the table, omitting the rest
of the headline.
Patch below.
BR,
Martin
>From 1228efc453d38bc090511f21fafa750e416e8b7a Mon Sep 17 00:00:00 2001
From: Martin Kampas
> Fixed. Thank you.
Thanks!
Alex
Hello,
Alex Branham writes:
> On Fri 20 Apr 2018 at 04:27, Nicolas Goaziou wrote:
>
>>> #+BEGIN_EXAMPLE
>>> #+TAGS: office(c) car(C)
>>> * one
>>> #+END_EXAMPLE
>>
>> FWIW, I couldn't reproduce it on master.
>
> It seems to be a problem with
Nicolas Goaziou writes:
I think this is now fixed. Thank you.
Yes, I see it as fixed, tested with git clone which gave me:
Org mode version 9.1.10 (release_9.1.10-619-g02e290 @
/Users/iam/.emacs.d/lisp/org-mode/lisp/)
Thank you.
--
Brady
Hello,
Brady Trainor writes:
> The issue at following thread seems to have resurfaced
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2016-07/msg00490.html
>
> If I run the following
>
> emacs -Q -nw --eval "(progn (setq org-capture-templates '((\"t\"
> \"Task\" entry
The issue at following thread seems to have resurfaced
https://lists.gnu.org/archive/html/emacs-orgmode/2016-07/msg00490.html
If I run the following
--8<---cut here---start->8---
emacs -Q -nw --eval "(progn (setq org-capture-templates '((\"t\"
\"Task\"
On Fri 20 Apr 2018 at 04:27, Nicolas Goaziou wrote:
>> #+BEGIN_EXAMPLE
>> #+TAGS: office(c) car(C)
>> * one
>> #+END_EXAMPLE
>
> FWIW, I couldn't reproduce it on master.
It seems to be a problem with org-tag-persistent-alist. I can't
reproduce it if that's nil, but
On Fri 20 Apr 2018 at 04:27, Nicolas Goaziou wrote:
>> I'm tracking maint. With the following file:
>>
>> #+BEGIN_EXAMPLE
>> #+TAGS: office(c) car(C)
>> * one
>> #+END_EXAMPLE
>
> FWIW, I couldn't reproduce it on master.
That's surprising, since I can reproduce this
Hello,
Sebastian Reuße writes:
> As for my 5 cents on the (probably not too consequential) design issue:
> I’d probably choose to treat this as an empty headline with tags. Due to
> the special syntax, tags are “more special” than headlines, and my
> expectation would be that
Hello,
Alex Branham writes:
> I'm tracking maint. With the following file:
>
> #+BEGIN_EXAMPLE
> #+TAGS: office(c) car(C)
> * one
> #+END_EXAMPLE
FWIW, I couldn't reproduce it on master.
Regards,
--
Nicolas Goaziou
Hello,
Rainer Stengele writes:
> Am 11.04.2018 um 11:50 schrieb Rainer Stengele:
>> All,
>>
>> I have a simple Org file with this content:
>>
>> * TODO Test agenda clockings
>> CLOCK: [2018-04-11 Mi 11:30]--[2018-04-11 Mi 11:45] => 0:15
>> CLOCK: [2018-04-10 Di
Am 11.04.2018 um 11:50 schrieb Rainer Stengele:
All,
I have a simple Org file with this content:
* TODO Test agenda clockings
CLOCK: [2018-04-11 Mi 11:30]--[2018-04-11 Mi 11:45] => 0:15
CLOCK: [2018-04-10 Di 11:30]--[2018-04-10 Di 11:45] => 0:15
CLOCK: [2018-04-09 Mo
Hello,
wang jinjian writes:
> Use case is call dot babel from elisp code block. refer to
> http://orgmode.org/worg/org-tutorials/org-dot-diagrams.html
>
> Below is a more minimal example:
>
> #+NAME: nodes
> | From | To | Weight |
>
> |--++|
> | A| B |
Hello,
Daniel P Gomez writes:
> I was thinking of #+ignore_tags. as an analog of #+exclude_tags. While
> #+exclude_tags removes a complete subtree from export, #+ignore_tags
> would only ignore headlines and insert the contents.
You may want to read the discussions about
Vladimir Lomov writes:
> I thought that for software versions 9.1 < 9.1.9 and means that 9.1
> preceding the 9.1.9.
We are not talking about software version but manual version.
> And first thing that comes to my mind about recent
> changes is a "template" system, there was
Hello,
** Nicolas Goaziou [2018-04-14 16:43:31 +0200]:
> Vladimir Lomov writes:
>
>> Earlier there was "full" "git" version in Manual and I found it convenient
>> (I read the manual from time to time to find how to do something in org)
>> but now when I open Info with Org
Vladimir Lomov writes:
> Earlier there was "full" "git" version in Manual and I found it convenient
> (I read the manual from time to time to find how to do something in org)
> but now when I open Info with Org manual I'm a bit puzzled, it shows
> version 9.1 while Org from
Hello,
** Nicolas Goaziou [2018-04-13 19:37:09 +0200]:
> Hello,
>
> Vladimir Lomov writes:
>
>> I'm using org-mode from git and found that now it is not show the
>> 'git' version but simply 9.1 in Info file. In doc/ there is
>> 'org-version.inc', it is included into
Hello,
Vladimir Lomov writes:
> I'm using org-mode from git and found that now it is not show the
> 'git' version but simply 9.1 in Info file. In doc/ there is
> 'org-version.inc', it is included into 'orgguide.texi' but not in
> 'org.texi'.
>
> As I understand the
Hello,
I'm using org-mode from git and found that now it is not show the
'git' version but simply 9.1 in Info file. In doc/ there is
'org-version.inc', it is included into 'orgguide.texi' but not in
'org.texi'.
As I understand the 'org.texi' is generated from 'org-manual.org', so
'org-manual.org'
I was thinking of #+ignore_tags. as an analog of #+exclude_tags. While
#+exclude_tags removes a complete subtree from export, #+ignore_tags
would only ignore headlines and insert the contents.
When used in combination, subtree would be excluded no matter what.
#+IGNORE_TAGS: ignore bar
Thanks, indeed. I will contact the maintainer.
Giuseppe Lipari
Le jeu. 12 avr. 2018 à 15:40, Nicolas Goaziou a
écrit :
> Hello,
>
> Giuseppe Lipari writes:
>
> > Dear all,
> >
> > (I am reposting it here with a more appropriate subject-line,
Hello,
Sebastian P. Luque writes:
> ╭─ [ emacs_init.el ]
> │ (package-initialize)
> │ (toggle-debug-on-error)
> │ (setq org-startup-align-all-tables t)
> ╰─
>
> First line is to ensure the Elpa Org package is available.
>
> ╭─ [ bug.org ]
> │ * Column width
Hello,
Giuseppe Lipari writes:
> Dear all,
>
> (I am reposting it here with a more appropriate subject-line, hoping to get
> more attention)
>
> Consider the following org file:
>
> * An example of org file
>
> Here I put a C snippet
>
> #+BEGIN_SRC c
> int main() {
>
Hello,
"Daniel P. Gomez" writes:
> Is there any intention of bringing ox-extra functionality into main
> Org? Something like #+ignore_tags would be a powerful addition for
> fine grained export control, in my opinion.
IIRC, "ox-extra" was written because we could not
Hi all,
TLDR: Using ox-extras :IGNORE: tags break #+INCLUDE :minlevel.
Ideally ox-extras functionality could make it into ox.
I'm using Org Mode to structure my thesis, and one of the Org
features that I rely on the most are the #+INCLUDE derivatives.
My setup is such that I have a main
Hello,
Robert Irelan writes:
> Hi, that ended up being the problem. Specifically, the line at
> https://code.orgmode.org/bzg/org-mode/src/442e7a2911e3e0229b1b6dd1fe0449653274ec31/lisp/org-capture.el#L1013
> needs to be fixed to read instead
>
> (append `(0 0
On Wed, 11 Apr 2018 13:17:49 +0200,
Nicolas Goaziou wrote:
> Hello, "Sebastian P. Luque" writes:
>> When `org-startup-align-all-tables' is t, then editing the cookie
>> in a table causes subsequent tabbing inside the table to throw the
>> following
Hello,
"Sebastian P. Luque" writes:
> When `org-startup-align-all-tables' is t, then editing the cookie in
> a table causes subsequent tabbing inside the table to throw the
> following trace:
>
> Debugger entered--Lisp error: (args-out-of-range #("abcde" 0 1 (help-echo
>
All,
I have a simple Org file with this content:
* TODO Test agenda clockings
CLOCK: [2018-04-11 Mi 11:30]--[2018-04-11 Mi 11:45] => 0:15
CLOCK: [2018-04-10 Di 11:30]--[2018-04-10 Di 11:45] => 0:15
CLOCK: [2018-04-09 Mo 11:30]--[2018-04-09 Mo 11:45] => 0:15
CLOCK: [2018-04-08 So
> Org-mode seems to support environment-based math formulas. However, when
> using pmatrix, the buffer *Org PDF LaTeX Output* always shows an
> error when exporting to PDF via LaTeX. This even happens for the
> simplest of matrices:
>
> \begin{pmatrix}
> 0
> \end{pmatrix}
>
> An org file with only
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hello,
When `org-startup-align-all-tables' is t, then editing the cookie in
a table causes subsequent tabbing inside the table to throw the
following trace:
------
Debugger entered--Lisp error: (args-out-of-range #("abcde" 0 1
Hi, that ended up being the problem. Specifically, the line at
https://code.orgmode.org/bzg/org-mode/src/442e7a2911e3e0229b1b6dd1fe0449653274ec31/lisp/org-capture.el#L1013
needs to be fixed to read instead
(append `(0 0 ,org-extend-today-until)
On Sat, Apr 7, 2018 at 2:07 PM Nicolas Goaziou
Hi Nicolas,
All of that sounds reasonable. Thanks for the reply.
-Brent
On Sun, Apr 8, 2018, 9:43 AM Nicolas Goaziou wrote:
> Hello,
>
> Brent Goodrick writes:
>
> > First, it may be a separate "bug" that org-return cannot recognize the
> >
Hello,
Brent Goodrick writes:
> First, it may be a separate "bug" that org-return cannot recognize the
> multi-line Org link.
Fixed. Thank you.
> I don't know one way or the other for that, but instead I am arguing
> that org mode's fill paragraph function should never break
This is not a new bug. It has been there for a long time, but I am
only just now getting around to reporting it. I am also proposing a
fix below.
How to reproduce:
Open up a Org mode file and add the following item to it:
Hi Nicolas,
* Gregor Zattler [2018-04-07; 22:30]:
> * Nicolas Goaziou [2018-04-03; 22:05]:
>> There is no such thing as a "%I" placeholder. Do you mean "%I"?
>
> Yes, I mean %i, the capital %I in this quote is --as I realize
> now, while typing this
Hello,
Robert Irelan writes:
> I have an org-capture template of type file+olp+datetree and :time-prompt
> t. Whenever I invoke it, it prompts me for a date. If I enter the current
> date at the prompt, `%u` correctly formats the captured entry with today's
> date. However,
Hi Nicolas,
* Nicolas Goaziou [2018-04-03; 22:05]:
> Gregor Zattler writes:
>
>> Yes, sure. Sorry, for my laziness. None of my templates work any more
>> with git master. This is a (for privacy reasons) shortend version of
>> my customizations, done
Leo Vivier writes:
> Hello,
>
> Thank you for pointing me in the right direction. I've created another
> init file just for async-export, and not only have I got it to work,
> but it's also quite a lot faster than it used to be.
>
> All that remains now is to find a way to
Leo Vivier writes:
> Hello,
>
> Thank you for pointing me in the right direction. I've created another
> init file just for async-export, and not only have I got it to work, but
> it's also quite a lot faster than it used to be.
>
> All that remains now is to find a way
Hello,
Thank you for pointing me in the right direction. I've created another
init file just for async-export, and not only have I got it to work, but
it's also quite a lot faster than it used to be.
All that remains now is to find a way to re-write my function. My
knowledge of elisp if
Hello,
Leo Vivier writes:
> I've encountered an issue trying to write a function to toggle between
> two org-latex-pdf-process states (short & long). The function works as
> intended when using synchronous export (the PDF is created with the
> appropriate number of steps),
After 'M-x org-tags-view c-g', there is a empty buffer named *Org Agenda*
left, which is unwanted to me.
Hi,
I've encountered an issue trying to write a function to toggle between
two org-latex-pdf-process states (short & long). The function works as
intended when using synchronous export (the PDF is created with the
appropriate number of steps), but it doesn't work with asynchronous
export
So I just searched the org sources and stumbled upon
org-latex-prefer-user-labels, which needs to be t for this to work in
newer emacs versions.
Sorry for the noise
On Fri, Apr 6, 2018 at 10:28 AM, beckonsmorbid wrote:
> Emacs : GNU Emacs 27.0.50 (build 1,
Emacs : GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.29)
of 2018-04-05
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/usr/share/emacs/27.0.50/lisp/org/)
--
Hi,
It
1001 - 1100 of 9192 matches
Mail list logo