Hello,
Stig Brautaset writes:
> Stig Brautaset writes:
>
>> I just noticed that all my property drawers have become
>> right-aligned, except the contents _inside_ them, which is still
>> where it previously was. All my agenda entries now have their
>> start/end markers right-aligned like this. (
Eric Abrahamsen writes:
> Carsten Dominik writes:
>
>> Dear all,
>>
>> before continuing this discussion, and before reinventing, you might
>> want to take a look at how org-id.el currently does create unique IDs.
>> [...]
>> Hope this helps.
>
> Right, and we're not trying to reinvent any wheel
Stig Brautaset writes:
> I just noticed that all my property drawers have become
> right-aligned, except the contents _inside_ them, which is still
> where it previously was. All my agenda entries now have their
> start/end markers right-aligned like this. (I only just learnt
> about org-habit.el
I just noticed that all my property drawers have become
right-aligned, except the contents _inside_ them, which is still
where it previously was. All my agenda entries now have their
start/end markers right-aligned like this. (I only just learnt
about org-habit.el)
,
| ** TODO Write sho
Carsten Dominik writes:
> Dear all,
>
> before continuing this discussion, and before reinventing, you might
> want to take a look at how org-id.el currently does create unique IDs.
> In particular, take a look at these variables:
>
> org-id-prefix
> org-id-method
> org-id-include-domain
>
> In
And one more remark.
A main reason for the CUSTOM_ID (and my only use of it, really) it to make
HTML targets stable and meaningful. In the following file
*
*
:PROPERTIES:
:CUSTOM_ID: Lotsofbshere
:END:
you can have a stable link
to file.html#Lotsofbshere
Carsten
On Thu, Dec
Dear all,
before continuing this discussion, and before reinventing, you might want
to take a look at how org-id.el currently does create unique IDs. In
particular, take a look at these variables:
org-id-prefix
org-id-method
org-id-include-domain
In particular, the docstring of the variable org
Matthew Pritchard writes:
> I can’t issue the push command on my system I am using emacs OS X
> 25.11 and the latest org on osx. I expect that a package is missing as
> the culprit. Any help would be appreciatied.
>
Matthew,
You have been posting questions about mobile-org on the list for a
whi
Christophe Schockaert writes:
> Eric Abrahamsen writes:
>
>> Karl Voit writes:
>>
>>> I'd prefer using manually written :ID: instead since migration would
>>> not be trivial to me.
>>
>> You could also use the `org-property-set-functions-alist' trick with the
>> :ID: property. If you added an "I
Eric Abrahamsen writes:
> Karl Voit writes:
>
>> I'd prefer using manually written :ID: instead since migration would
>> not be trivial to me.
>
> You could also use the `org-property-set-functions-alist' trick with the
> :ID: property. If you added an "ID" entry to that alist, Org's usual
> aut
I can’t issue the push command on my system I am using emacs OS X 25.11 and the
latest org on osx. I expect that a package is missing as the culprit. Any help
would be appreciatied.
John Kitchin writes:
> On Thu, Dec 22, 2016 at 10:30 AM, Karl Voit wrote:
>
>> * John Kitchin wrote:
>> >
>> > There is not an issue using a human-readable id in :ID: as long as it is
>> > unique. It will store fine, link fine, etc...
>>
>> I also think so because I am only using human-readable
an example of a custom id feature might be for export. sounds like
you might not need it.
On 12/22/16, Karl Voit wrote:
> However, the argument was that no human should set :ID: but use
> :CUSTOM_ID: *instead*. See also the old thread I linked before.
i don't recall anybody arguing, claiming, or implying specifically that.
if you're careful, and do not need custom id features, then y
I've not encountered this issue before, but on a git pull last night I
was greeted with a message like this (I don't have the original which
listed several other branches):
$ git pull
>From http://orgmode.org/org-mode
13751c3249..820d1eb617 maint -> origin/maint
7fd61c4f92..1c89082600
On Thu, Dec 22, 2016 at 10:29 AM, John Hendy wrote:
> Greetings,
>
>
> I'm finishing up a 30 page end of year work report and perhaps
> stupidly decided I'd git pull on my various emacs packages last night.
> I went to work on it today and I'm getting the following error:
>
> C-c C-e l p
> shell-q
I'd been looking into debugging in a separate tab, got distracted, and
sent this after forgetting I was going to do that. My apologies for
the second email... I followed the feedback instructions and got this
output:[1]
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
replace-regex
Greetings,
I'm finishing up a 30 page end of year work report and perhaps
stupidly decided I'd git pull on my various emacs packages last night.
I went to work on it today and I'm getting the following error:
C-c C-e l p
shell-quote-argument: Wrong type argument: arrayp, nil
I fiddled with tagg
Karl Voit writes:
> * John Kitchin wrote:
>>
>> There is not an issue using a human-readable id in :ID: as long as it is
>> unique. It will store fine, link fine, etc...
>
> I also think so because I am only using human-readable :ID: without
> any issue so far.
>
> However, the argument was that
That is just be a convention though, and as long as the IDs are unique, it
does not matter who sets them.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
* John Kitchin wrote:
>
> There is not an issue using a human-readable id in :ID: as long as it is
> unique. It will store fine, link fine, etc...
I also think so because I am only using human-readable :ID: without
any issue so far.
However, the argument was that no human should set :ID: but use
There is not an issue using a human-readable id in :ID: as long as it is
unique. It will store fine, link fine, etc...
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
Hello,
Christian Wittern writes:
> I came across a typo that makes exporting to Latex impossible. The
> attached patch fixes this problem.
Thank you. However, I fixed it a couple of hours ago.
Regards,
--
Nicolas Goaziou
Hello,
"Holst Thomas (DGS-EC/ESE4)" writes:
> with latest org from git I get an error when trying to export to pdf:
>
> shell-quote-argument: Wrong type argument: arrayp, nil
This is already fixed in maint branch.
Regards,
--
Nicolas Goaziou
Hi all
i recently had some projects where i would define the overall project as a
TODO and then add some more sub headers with TODOS. the problem is that i
dont want to see all these sub TODOS in the agenda. For example:
* TODO start writing paper
** TODO collect data
** TODO add refernces
...
In case you do have access to your mail server:
* Xebar Saram wrote:
>
> im looking for a simple solution that will allow me to send an email from
> my mobile phone and habr that email either be appended to a txt(org) file
> or perhaps another solution to get my mobile on the go notes onto my lap
Dear Org List,
I came across a typo that makes exporting to Latex impossible. The attached
patch fixes this problem.
This is the first patch I submit, and I changed just one line. If there is a
problem, you can just fix this one place manually.
All the best,
Christian
--
Christian Wittern
Hi,
with latest org from git I get an error when trying to export to pdf:
shell-quote-argument: Wrong type argument: arrayp, nil
bisecting shows:
91dc1b34e3033c56b71fca16d8b9403c3585c66e is the first bad commit
commit 91dc1b34e3033c56b71fca16d8b9403c3585c66e
Author: Nicolas Goaziou
Date: Tu
* Karl Voit wrote:
> * Samuel Wales wrote:
>> On 12/18/16, Karl Voit wrote:
>>> Usually, my IDs start with the current ISO day to enforce uniqueness
>>> and look like this:
>>
>> my understanding, which might be incorrect, is that custom id is for
>> human-readable purposes, while id is for
29 matches
Mail list logo
