Re: [O] clock-table property column empty

[Nikolay Kudryavtsev]

Ok, this was due to me not running make in the repo first.

Still I have another problem - I get two extra columns in the 
clocktable. See the attached test.org file.


--
Best Regards,
Nikolay Kudryavtsev

** TODO Test  :test:
:PROPERTIES:
:key:  123
:END:
:LOGBOOK:
CLOCK: [2017-05-24 Ср 21:08]--[2017-05-24 Ср 22:08] =>  1:00
:END:
** Clocktable
#+BEGIN: clocktable :maxlevel 4 :scope file :tags "test" :properties ("key")
#+CAPTION: Clock summary at [2017-05-25 Чт 03:51]
| key | Headline | Time   |  |   |   |
|-+--++--+---+---|
| | *Total time* | *1:00* |  |   |   |
|-+--++--+---+---|
| 123 | \_  Test || 1:00 |   |   |
#+END

Re: [O] clock-table property column empty

[Nicolas Goaziou]

Hello,

Nikolay Kudryavtsev  writes:

> I've just tried the repo at 30ceb5c7942b5804b2bba18ce3e08124add0d278.
> That is master ATM
>
> Clocktables do not seem to work there at all.

All the clock table tests pass, according to our build bot, so there is
certainly something that does work.

What did you try? What happened?

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] clock-table property column empty

[Nikolay Kudryavtsev]

I've just tried the repo at 30ceb5c7942b5804b2bba18ce3e08124add0d278. 
That is master ATM


Clocktables do not seem to work there at all.|
|

||Also it seems that remote |git://orgmode.org/org-mode.git does not 
currently work. http://|||orgmode.org/org-mode.git| works.|

||

--
Best Regards,
Nikolay Kudryavtsev

[O] Show all timestamps in agenda custom command

[Thorsten Grothe]

Hello,

I would like to generate a agenda custom command which shows me always
*all* timestamps (with deadline and scheduled too) of todo items.

See this examples:

For this entry it works fine:
** TODO <2017-05-29 Mo> Test entry

it looks like this:
  TODO <2017-05-29> Test entry
  
but not for scheduled entries like this with linebreak:

** TODO Test
SCHEDULED: <2017-05-24 Mi>

Org agenda only shows this:
SCHULE Test → where's the timestamp?

I would like the see the timestamp like in the example above.

This is my agenda custom command so far:

...
("s" "Schule" todo "SCHULE"
   ((org-agenda-overriding-header "Schule")
(org-agenda-prefix-format "○  %t%s")
(org-agenda-entry-types '(:scheduled))
   ))
...

what can I do to solve this problem?


Regards

Thorsten Grothe

Re: [O] Documentation fix

[Nicolas Goaziou]

Hello,

Colin Baxter  writes:

> I've appended (inline) the warnings associated with the documentation output
> of 'make all', removing extraneous output.
>
>  Begin 
> org-version: 9.0.7 (release_9.0.7-478-g30ceb5)
> makeinfo --no-split org.texi -o org
> makeinfo --html --number-sections --no-split -o org.html org.texi
> texi2pdf --batch --clean --expand org.texi
> -:1267: warning: @itemx should not begin @table
> -:1345: warning: @table has text but no @item

[...]

>
> The 'make all' process continues satisfactorily to its conclusion.

These are innocuous warnings.  

> Deleting the 'x' from 'itemx' in org.texi at the lines corresponding to the
> warnings '@itemx should not begin @table', that is, at lines 1267, 7819, 
> 10342,
> removes those warnings. That's all the patch did.

This would be wrong. The @orgcmd macro above already introduces @item,
so the second one really needs to be @itemx.

One solution would be to replace the @itemx ... with @xorgkey, @xorgcmd,
or @xorgcmdnki depending on the needs. But then, it would fall-back to
the other warning, i.e., a @table without any @item (all are
@orgsomething macros).

I'm no Texinfo expert, so I'm not sure what is the best way to handle
this. Maybe also create a special macro that would create a table. It
sounds convoluted, though.

Regards,

-- 
Nicolas Goaziou

Re: [O] Documentation fix

[Colin Baxter]

Dear Nicolas,

> "NG" == Nicolas Goaziou  writes:

NG> Hello, Colin Baxter  writes:

>> I have attached the warnings when making the documentation using
>> texi2any (GNU texinfo) 6.0, and a patch for the two '@itemx
>> should not begin @table' warnings. I am no expert on makeinfo and
>> I just removed the 'x' from 'itemx', so the patch is trivial.
>> 
>> I'm not having any luck with the multiple warning: '@table has
>> text but no @item' warnings. They don't make much sense to me.
>> 
>> Since the docs make satisfactorily with the warnings, perhaps a
>> note in the documentation might suffice, to the effect that later
>> versions of texinfo may produce ignorable warnings.

NG> I'm unable to open the document you sent. I looks like they are
NG> not properly attached to the mail. Could you send them again?

NG> Regards,

NG> -- Nicolas Goaziou 0x80A93738

Sorry about my previous email.

I've appended (inline) the warnings associated with the documentation output
of 'make all', removing extraneous output.

 Begin 
org-version: 9.0.7 (release_9.0.7-478-g30ceb5)
makeinfo --no-split org.texi -o org
makeinfo --html --number-sections --no-split -o org.html org.texi
texi2pdf --batch --clean --expand org.texi
-:1267: warning: @itemx should not begin @table
-:1345: warning: @table has text but no @item
-:1370: warning: @table has text but no @item
-:1416: warning: @table has text but no @item
-:1558: warning: @table has text but no @item
-:1701: warning: @table has text but no @item
-:2837: warning: @table has text but no @item
-:2894: warning: @table has text but no @item
-:3146: warning: @table has text but no @item
-:4796: warning: @table has text but no @item
-:4933: warning: @table has text but no @item
-:5223: warning: @table has text but no @item
-:5454: warning: @table has text but no @item
-:5808: warning: @table has text but no @item
-:6177: warning: @table has text but no @item
-:6308: warning: @table has text but no @item
-:6485: warning: @table has text but no @item
-:6831: warning: @table has text but no @item
-:6891: warning: @table has text but no @item
-:6910: warning: @table has text but no @item
-:6994: warning: @table has text but no @item
-:7402: warning: @table has text but no @item
-:7590: warning: @table has text but no @item
-:7819: warning: @itemx should not begin @table
-:7838: warning: @table has text but no @item
-:7854: warning: @table has text but no @item
-:7949: warning: @table has text but no @item
-:8107: warning: @table has text but no @item
-:8173: warning: @table has text but no @item
-:8342: warning: @table has text but no @item
-:8726: warning: @table has text but no @item
-:9499: warning: @table has text but no @item
-:9569: warning: @table has text but no @item
-:9636: warning: @table has text but no @item
-:10342: warning: @table has text but no @item
-:10919: warning: @table has text but no @item
-:11233: warning: @table has text but no @item
-:11304: warning: @table has text but no @item
-:12533: warning: @table has text but no @item
-:13462: warning: @table has text but no @item
-:13881: warning: @table has text but no @item
-:14782: warning: @table has text but no @item
-:17653: warning: @table has text but no @item
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
 restricted \write18 enabled.
entering extended mode
-- Cut -

The 'make all' process continues satisfactorily to its conclusion.

Deleting the 'x' from 'itemx' in org.texi at the lines corresponding to the
warnings '@itemx should not begin @table', that is, at lines 1267, 7819, 10342,
removes those warnings. That's all the patch did.

Best wishes,

Colin.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]

[Kaushal Modi]

On Wed, May 24, 2017 at 9:50 AM Chunyang Xu  wrote:

>
> Nicolas Goaziou writes:
>
> > Hello,
> >
> > 林镇国  writes:
> >
> >> When I insert a link to my note, such as“这是一个[[link][链接]]啦~”，
> >> the text after the link, "啦~", will be formatting as link style.
> >
> > FWIW, I cannot reproduce it, i.e., only "链接" appears with a link face.
>
> I can reproduce if "link" is a real link and "description" doesn't
> contain white space, for example,
>
> [[http://example.com/][Example]]blah
> 
> Also under the org-link face
>
> It looks like `org-plain-link-re' doesn't think a link is end unless
> a punctuation character is found:
>
> org-plain-link-re
> (concat
>  "\\<" types-re ":"
>  "\\([^ \t\n()<>]+\\(?:([[:word:]0-9_]+)\\|\\([^[:punct:]
> \t\n]\\|/\\)\\)\\)")
>   ^
>
> It is a reasonable assumption for English, but not for Chinese.
>

I actually stumbled across this few days back, and when using English
language :)

Here's a solution that might work for you too (and my notes on why I set
this):

;; The default value of `org-highlight-links' contains `plain' too.
;; - "plain" links are links in normal text, no whitespace, like
http://foo.com.
;; Here's why I remove "plain" from this list:
;; - If I have two bracketed links next to each-other in org-mode (like
below),
;; [[http://google.com][1]],[[http://orgmode.org][2]]
;; - and, if `plain' is in the `org-highlight-links' list,
;;  the "," in there will also be highlighted as a link. So it would look
;;  as if the "1,2" string pointed to a single link!
;;But without `plain' as part of this list, the "1" and "2" strings will
;; look like separate links (as should be the case), as the "," will not be
;; highlighted as a link.
(setq org-highlight-links (delete 'plain org-highlight-links))


-- 

Kaushal Modi

Re: [O] Bug: link formating problem [9.0.5 (9.0.5-elpaplus @ /Users/mistkafka/.emacs.d/elpa/org-plus-contrib-20170210/)]

[Chunyang Xu]

Nicolas Goaziou writes:

> Hello,
>
> 林镇国  writes:
>
>> When I insert a link to my note, such as“这是一个[[link][链接]]啦~”，
>> the text after the link, "啦~", will be formatting as link style.
>
> FWIW, I cannot reproduce it, i.e., only "链接" appears with a link face.

I can reproduce if "link" is a real link and "description" doesn't
contain white space, for example,

[[http://example.com/][Example]]blah

Also under the org-link face

It looks like `org-plain-link-re' doesn't think a link is end unless
a punctuation character is found:

org-plain-link-re
(concat
 "\\<" types-re ":"
 "\\([^ \t\n()<>]+\\(?:([[:word:]0-9_]+)\\|\\([^[:punct:] \t\n]\\|/\\)\\)\\)")
  ^

It is a reasonable assumption for English, but not for Chinese.

> Regards,