Re: [O] How remove time from date-time stamp

2019-04-08 Thread Fraga, Eric
On Monday,  8 Apr 2019 at 23:56, Thomas Plass wrote:
> However, if you want to directly change timestamps in the buffer they
> live (not: an agenda view), then S-right/left/up/down can call a hook
> function that does what you're trying to achieve.

Or simply C-d (or DEL or BS) 5 times?  "It's all text."

-- 
Professor Eric S Fraga, http://www.ucl.ac.uk/~ucecesf


[O] Bug: Capture prepend checkbox doesn't handle scheduled [9.2.3 (9.2.3-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20190402/)]

2019-04-08 Thread Allen Li
Make file /tmp/tmp.org containing:

* TODO Foo
SCHEDULED: <2019-04-08 Mon>

1. emacs -Q
2. Eval

(add-to-list 'load-path (expand-file-name
"~/.emacs.d/elpa/org-plus-contrib-20190402/"))
(setq org-capture-templates '(("c" "Capture" checkitem (file+headline
"/tmp/tmp.org" "Foo") "" :prepend t)))

3. M-x org-capture RET c
4. foo C-c C-c

Contents of tmp.org:

* TODO Foo
- [ ] foo
SCHEDULED: <2019-04-08 Mon>

Expected:

* TODO Foo
SCHEDULED: <2019-04-08 Mon>
- [ ] foo

prepend checkitem should also skip any property drawer in addition to
the planning line.

This bug does not happen if the headline already contains a checkbox
list item.

I cannot reproduce this with the Org mode that ships with Emacs, so
it's probably a regression?

Emacs  : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.22.24), modified by Debian
Package: Org mode version 9.2.3 (9.2.3-elpaplus @
~/.emacs.d/elpa/org-plus-contrib-20190402/)



[O] Possible bug (?): :noweb doesn't respect indentations (at least i R/BUGS/JAGS).

2019-04-08 Thread Emmanuel Charpentier
Compare this org source:

===
# A small :noweb mystery: indentation

#+property: header-args:R :session
#+options: toc:nil
#+author:
#+date:

The structure of a probablity proble can be represented by a ~JAGS~
code snippet:
#+name: Struct
#+begin_src R :eval never :exports code
  for (i in 1:nObs) {
for (j in 1:nZ) {
  Z[i,j] ~ dbern(P[i,j])
  logit(P[i,j]) <- alpha + beta[j]*X[i]
}
  }
#+end_src

The same code snippet can be used for simulation:

#+begin_src R :exports code :results none :noweb yes
  library(rjags)
  library(coda)
  ## Reproducibility ?
  set.seed(813)
  Params <- local({
nObs <- 500
nZ <- 5
X <- rnorm(nObs)
alpha <- rnorm(1,0,3)
beta <- rnorm(nZ,-1,2)
list(
  nObs=nObs,
  nZ=nZ,
  X=X,
  alpha=alpha,
  beta=beta)
  })
  ## Wrap model code
  M <-
"model {
 <>
  }"
  ## Compilation
  JM <- jags.model(textConnection(M), data=Params, n.adapt=1,
n.chains=1)
  ## Forward sampling
  JS <- coda.samples(JM, "Z", n.iter=1)
#+end_src

and for inference, after adding priors of parameters:

#+name: Priors
#+begin_src R :eval never :exports code
  ## Priors
  alpha ~ dt(0, 1e-2, 3)
  for (j in 1:nZ) {
beta[j] ~ dt(0,1e-2, 3)
  }
#+end_src

#+name: Inference
#+begin_src R :noweb yes :exports code
  Data <- list(
nObs=Params$nObs,
nZ=Params$nZ,
X=Params$X,
Z=matrix(as.matrix(JS), ncol=Params$nZ, byrow=FALSE))
  ## Wrap inference model
  MI <-
"model {
 <>
 <>
  }"
  ## Compilation
  JMI <- jags.model(textConnection(MI), Data, n.chains=4)
  ## Inference sampling
  JMS <- coda.samples(JMI, c("alpha", "beta"), n.iter=1000)
#+end_src

#+RESULTS: Inference
===

With the result of its export to Ascii:

===
The structure of a probablity proble can be represented by a `JAGS'
code
snippet:
,
| for (i in 1:nObs) {
|   for (j in 1:nZ) {
| Z[i,j] ~ dbern(P[i,j])
| logit(P[i,j]) <- alpha + beta[j]*X[i]
|   }
| }
`

The same code snippet can be used for simulation:

,
| library(rjags)
| library(coda)
| ## Reproducibility ?
| set.seed(813)
| Params <- local({
|   nObs <- 500
|   nZ <- 5
|   X <- rnorm(nObs)
|   alpha <- rnorm(1,0,3)
|   beta <- rnorm(nZ,-1,2)
|   list(
| nObs=nObs,
| nZ=nZ,
| X=X,
| alpha=alpha,
| beta=beta)
| })
| ## Wrap model code
| M <-
|   "model {
|for (i in 1:nObs) {
|for (j in 1:nZ) {
|  Z[i,j] ~ dbern(P[i,j])
|  logit(P[i,j]) <- alpha + beta[j]*X[i]
|}
|}
| }"
| ## Compilation
| JM <- jags.model(textConnection(M), data=Params, n.adapt=1,
n.chains=1)
| ## Forward sampling
| JS <- coda.samples(JM, "Z", n.iter=1)
`

and for inference, after adding priors of parameters:

,
| ## Priors
| alpha ~ dt(0, 1e-2, 3)
| for (j in 1:nZ) {
|   beta[j] ~ dt(0,1e-2, 3)
| }
`

,
| Data <- list(
|   nObs=Params$nObs,
|   nZ=Params$nZ,
|   X=Params$X,
|   Z=matrix(as.matrix(JS), ncol=Params$nZ, byrow=FALSE))
| ## Wrap inference model
| MI <-
|   "model {
|for (i in 1:nObs) {
|for (j in 1:nZ) {
|  Z[i,j] ~ dbern(P[i,j])
|  logit(P[i,j]) <- alpha + beta[j]*X[i]
|}
|}
|## Priors
|alpha ~ dt(0, 1e-2, 3)
|for (j in 1:nZ) {
|beta[j] ~ dt(0,1e-2, 3)
|}
| }"
| ## Compilation
| JMI <- jags.model(textConnection(MI), Data, n.chains=4)
| ## Inference sampling
| JMS <- coda.samples(JMI, c("alpha", "beta"), n.iter=1000)
`
===

The indentation is not respected in the included JAGS snippets. Further
attempts with exporting to PDF (both the built-in exporter and ox-
pandoc) and DOCX (ox-pandoc) show that the problem remains the same,
but, IIRC, with slight variations in whitespace.

That's not serious (just ugly) for R/JAGS ; but it might be serious for
Python/Sage, where whitespace is syntaxic.

Thoughts ?

--
Emmanuel Charpentier





Re: [O] sort headers by tags possible?

2019-04-08 Thread Kyle Meyer
Xebar Saram  writes:

> Hi all
>
> does anyone know if its possible to sort headers by tags?
> lets say i have this
>
> * header 1 . :3star:
> * header 2 . :4star:
> * header 3 . :3star:
>
> can i sort by tags (alphnumeric) so all 3star tags with start followed by
> 4star etc

Try calling org-sort and sorting on the TAGS property: `C-c ^ r` then
selecting "TAGS".

Offhand I don't know how that handles multiple tags, but, if that
doesn't do what you want, you can always supply a custom key and/or
comparison function to org-sort-entries (even when calling it
interactively).

-- 
Kyle



Re: [O] How remove time from date-time stamp

2019-04-08 Thread Thomas Plass
Detlef,

Detlef Steuer wrote at 14:36 on April 8, 2019:
: When in agenda view I can use C-k to kill an entry
: or S-right to promote to next day etc.
: 
: What I need really often in my workflow is the
: promotion to another day, but without the time part of the time stamp

This type of remote edit won't be possible without rewriting Org code.

However, if you want to directly change timestamps in the buffer they
live (not: an agenda view), then S-right/left/up/down can call a hook
function that does what you're trying to achieve.

Thomas




[O] sort headers by tags possible?

2019-04-08 Thread Xebar Saram
Hi all

does anyone know if its possible to sort headers by tags?
lets say i have this

* header 1 . :3star:
* header 2 . :4star:
* header 3 . :3star:

can i sort by tags (alphnumeric) so all 3star tags with start followed by
4star etc

thx

best

Z


[O] Logging :LOGBOOK: entries to a heading in org-mode without TODO state changes

2019-04-08 Thread Daryl Manning
I have org-mode set up at the moment to log changes in my TODO states (at
the moment, TODO, CHASE, GAVE, KILL, DONE) as well as deadline changes and
reschedules into a logbook drawer. That's working great.

However, I have begun using org-contacts as an ersatz CRM for myself and
keeping track of mails, meets, and other administrivia tracking people I'm
interacting with.

I'd love to have a way to as easily use something CTRL-C-T and then have
the ability to log an item into a Logbook drawer under each heading name.

Is there a way to do this easily without hacking TODO states? Or are there
other ways people are doing this to achieve the same goal (I'm also hoping
to set PING deadlines on people so that I am making sure to recontact them
at various intervals over time, but still trying to puzzle that out... =]
).

Would love to know what other people have done with this that is
lightweight and practical.

thanks!
Daryl.


[O] Graphing upcoming scheduled items

2019-04-08 Thread Phillip Lord



Is there a way to get a list of the number of upcoming scheduled items?
I was looking for a sparse list and to an arbitrary time in the
future, and not specifically over my agenda files.

Something like:


01-04-201910
03-04-201914
...
01-08-20196
...
01-02-20204


I might write it myself, but if it's there already

Phil






[O] How remove time from date-time stamp

2019-04-08 Thread Detlef Steuer
Dear list,

looking for advice on a seemingly simple matter.

When in agenda view I can use C-k to kill an entry
or S-right to promote to next day etc.

What I need really often in my workflow is the
promotion to another day, but without the time part of the time stamp
I assigned for today.
Best would be some command like S-right , maybe C-u S-right,
to move the entry one or more days without the time information.

I seem to remember there was a discussion on this list about
such a feature but I'm unable to find it.

But maybe it's like always: the feature exists already somewherer in
org?!

What do you use to efficiently shift an entry, but strip its time?

Any help appreciated

Detlef

-- 
The biggest difference between time and space is that you can’t reuse
time. (Merrick Furst)




[O] scratching an itch: parenthesis matching in org

2019-04-08 Thread Fraga, Eric
Hello,

just in case this is helpful to anybody out there, one of the (very
minor) annoyances for me writing in org has been that org treats angle
brackets (<>) as parenthesis in terms of syntax.  I write a lot of
mathematics in my document and these are typically operators and seldom
intended as brackets.  Having these known as parentheses in org's syntax
table makes showing matching parentheses not work properly in most of my
documents.

Adding these two lines to my org mode hook:

(modify-syntax-entry ?< ".")
(modify-syntax-entry ?> ".")

fixes the behaviour.

I haven't seen any negative repercussions (yet...).

Itched satisfactorily scratched! :)

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.2.3-327-g3375f0



Re: [O] [ISSUE] links navigation not consistent behavior

2019-04-08 Thread Nicolas Goaziou
Hello,

stardiviner  writes:

> I'm using the latest commit of master branch of Org. Still have link 
> navigation problem.
>
> It used can treat http:// like url as link too. Now it is ignored. Is
> it on designed or an issue?

I don't understand your report. Please describe it with an example.
Thank you.

Regards,

-- 
Nicolas Goaziou