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

2019-04-09 Thread stardiviner


Nicolas Goaziou  writes:

> 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,


#+begin_src org


https://www.bing.com

,* link in properties drawer
  :PROPERTIES:
  :URL:  http://www.google.com
  :END:

https://www.bing.com
  
,* http(s) url in content of headline
  
https://www.baidu.com
#+end_src

In upper example, when I link jumping from first link to next, it will skip the
url in properties drawer.

When I try to jump backwards, some times reports "no further link found", like
when I'm on the last link.

-- 
[ stardiviner ]
   I try to make every word tell the meaning what I want to express.

   Blog: https://stardiviner.github.io/
   IRC(freenode): stardiviner, Matrix: stardiviner
   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
  



[O] BUG: org-archive-subtree LOSES DATA when run on unsaved buffer

2019-04-09 Thread Cook, Malcolm
Hi,

I never use org's archiving capabilities.

So imaging my surprise when I accidently invoked org-archive-subtree from its 
key-binding and I lost a whole subtree of a new buffer which (alas) I had not 
yet saved to disk

Further alas, I was so alarmed not knowing where my content disappeared to that 
I did not think to try the obvious - undo.

What happens?  It appears that org-archive-subtree will create a symlink to a 
non-existent target and try to move the subtree there (which does not make 
sense) and does not check for errors or confirm completion.

This arguably should be addressed.

This is emacs 26.1 running org-version 9.2.3-4

In the mean time...

Still livin' in emacs + Org,

~Malcolm



Re: [O] Emacs-orgmode Digest, Vol 158, Issue 9

2019-04-09 Thread Daryl Manning
Gregor,

First off, thank you for the Org Add note. I am embarrassed I did not know
about it, it is *exactly* what I want. Thanks! I will add it into a blog
post on my workflow when I go over contact management since I have to
admit, I googled quite a bit to find something and did not run across
org-add note until you mentioned it. Thank you.

As for Chase and Gave on my TODO states, these were originally WAIT and
GAVE for tasks I needed to chase people - I manage a large team that is
cross company so have numerous stakeholders and often off a mail or other
task have to chase someone for something they were either supposed to get
to me to make one of my deadlines or something else I need to make sure is
progressing or actually happened. I assign a deadline to that wait state
after I've executed something.

Subtly different is when I delegate something completely to one of my
reports (or another VP/ BU Head), and I give that a GAVE delegated state
with a DEADLINE on it in order to follow up or expect something being done.
The idea there is that I followup at that time expectint the thing to be
done or as a check-in towards an agreed completion date. It also helps when
I go over my 1:1s with them to understand what is on their plate.

I was going to try to use org-habit as you suggest so interested in greater
detail around rthe "clumsines you mention. I often use week tags ie. 'w15'
being this week, so that I can add that to some more random or automated
followups since it is a matter of making sure I do ping someone once in a
while rather than specific scheduled things. So, record a note, CTRL-c-q
the tag from the contact week like w15 to w19 or such and then it shows up
in the org-super-agenda-view I crafted on my weekly todo tasks rather than
a specific deadline or such. Do you think that  may work less clumisnly
than org-habit? (I know what you mean, I used org-habit in my last run at
habit tracking in org-mode but gave up and started using the excellent
habitctl command line tracker. Check it out, though it is not appropriate
to this task.).

Let me know if you want more detail on the above. The crafted super-agenda
view is what makes this work well since I have it auto sort the view to
give me todo items that are tagged for this week, but do not show up in the
agenda as they have dates attached through deadlines or schedules. So far,
so good on it working, but only crafted the view on the plane on Sunday so
need to see if this will work better than what I was doing before.  =]

thanks again for the Add Note hint! I cannot believe that that did not come
up in my searches on how to do this. Very handy!
Daryl.


On Tue, Apr 9, 2019 at 9:02 AM  wrote:

> Send Emacs-orgmode mailing list submissions to
> emacs-orgmode@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/emacs-orgmode
> or, via email, send a message with subject or body 'help' to
> emacs-orgmode-requ...@gnu.org
>
> You can reach the person managing the list at
> emacs-orgmode-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Emacs-orgmode digest..."
>
>
> Today's Topics:
>
>1. Logging :LOGBOOK: entries to a heading in org-mode without
>   TODO state changes (Daryl Manning)
> ...
>8. Re: Logging :LOGBOOK: entries to a heading in org-mode
>   without TODO state changes (Gregor Zattler)
>
>
> --
>
> Message: 1
> Date: Mon, 8 Apr 2019 22:46:42 +0700
> From: Daryl Manning
> To: emacs-orgmode@gnu.org
> Subject: [O] Logging :LOGBOOK: entries to a heading in org-mode
> without TODO state changes
> Message-ID:
>  mauhnkup...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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.
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> 

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

2019-04-09 Thread Emmanuel Charpentier
Thanks ! Ths switch excaped my attention, probably because it is buried
in a "literal example" section, which I didn't connect to noweb care
and feeding...

Maybe the "noweb" section might benefit of a discrete recall of
relevant switches ?

Thanks again !

--
Emmanuel Charpentier


Le mardi 09 avril 2019 à 16:19 +, Berry, Charles a écrit :
> > On Apr 8, 2019, at 4:01 PM, Emmanuel Charpentier <
> > emm.charpent...@free.fr> wrote:
> > 
> > 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:
> > 
> 
> See Org Manual (org) Literal Examples for information about the -i
> switch
> 
> Try: 
> 
> #+begin_src R -i :exports code :results none :noweb yes
> 
> instead of this:
> 
> > #+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
> > 
> 
> And again here:
> 
> 
> > #+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:
> > 
> 
> [snip]
> 
> 
> > 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 ?
> > 
> 
> Try the switch.
> 
> HTH,
> 
> Chuck




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

2019-04-09 Thread Berry, Charles



> On Apr 8, 2019, at 4:01 PM, Emmanuel Charpentier  
> wrote:
> 
> 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:
> 


See Org Manual (org) Literal Examples for information about the -i switch

Try: 

#+begin_src R -i :exports code :results none :noweb yes

instead of this:

> #+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
> 

And again here:


> #+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:
> 


[snip]


> 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 ?
> 


Try the switch.

HTH,

Chuck



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

2019-04-09 Thread Fraga, Eric
On Tuesday,  9 Apr 2019 at 09:22, Detlef Steuer wrote:
> Well, of course it's all text. But 5 times often is not enough,
> cause there are start and end times.
>
> Nevertheless that hint gave me the right direction:

Great.  I find that hint quite useful for me and have to keep reminding
myself.  The fancier org gets, the easier it is to forget this such
fundamental aspect which distinguishes it from most other tools.
-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.2.2-290-g300f15


Re: [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-09 Thread Nicolas Goaziou
Hello,

Allen Li  writes:

> 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

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



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

2019-04-09 Thread Detlef Steuer
Am Tue, 9 Apr 2019 05:27:50 +
schrieb "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."
> 

Well, of course it's all text. But 5 times often is not enough,
cause there are start and end times.

Nevertheless that hint gave me the right direction:

In the agenda hit return on an entry.
C-c . opens the interface to alter the timestamp.
C-a C-k (or C-0 C-k) deletes the time part.
Done! Easy enough.

Thank you!

If there were a solution without leaving agenda view, that would be
another big improvement (for me).

Detlef

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




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

2019-04-09 Thread Gregor Zattler
Hi Daryl,
* Daryl Manning  [2019-04-08; 22:46]:
> 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

would you please elaborate on the semantics of these (esp. chase,
gave)?

> 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.

There's org-add-note, bound by default to C-c C-z, which does
exactly that.  It even works from the agenda.

> 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... =]
> ).

I tried to use org-habit for this, but it gets clumsy, if you
want to contact somebody round about every 60 days or so.


Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-