Re: [O] [Patch] [Feature request] Add option to natively fontify latex snippets and environment

2019-01-14 Thread stardiviner


Carlos Pita  writes:

> Hi Nicolas,
>
> I was thinking that maybe it would be nicer to make this depend on the
> value of org-src-fontify-natively. What do you think?
>
> Regards

I don't think so. BTW, I found this patch cause my Org Mode buffer
fontify error.

After some raw latex block, all following fontify wrong. This is
happened when I use latest master branch a few days ago. I disable the
option to disable this fontify. I have `org-src-fontify-natively`
enabled by default. It might cause my Org Mode buffer fontify failed
again.

At least, I think this patch should need more test.

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



Re: [O] Paste subtree without expanding it / keep it collapsed after pasting

2019-01-14 Thread Kyle Meyer
Marcelo de Moraes Serpa  writes:

[...]

> I can copy or cut a collapsed subtree and it will copy everything below it
> until it ends (and the next item at the same level starts), which is
> intuitive and works great. However, when pasting it, it automatically
> expands the tree and it makes it really hard to see the context so I can
> fix the leveling, for example.
>
> Is there a way to paste the subtree [and keep it] collapsed?

I’m not able to trigger that behavior using the default configuration.
Here’s what I tried on both master and maint using the file below.

With point on the aa1 heading (collapsed), I pressed ‘C-c @’ followed by
‘C-w’.  I then moved point under the b heading and hit ‘C-y’.  aa1
stayed collapsed after it was yanked.

Does that sequence accurately reflect the scenario you’re describing?


--8<---cut here---start->8---
* a
** aa1

Lorem ipsum dolor sit amet, consectetuer adipiscing elit.  Donec
hendrerit tempor tellus.  Donec pretium posuere tellus.

Aliquam erat volutpat.  Nunc eleifend leo vitae magna.  In id erat non
orci commodo lobortis.  Proin neque massa, cursus ut, gravida ut,
lobortis eget, lacus.  Sed diam.

*** aaa1

Nullam eu ante vel est convallis dignissim.  Fusce suscipit, wisi nec
facilisis facilisis, est dui fermentum leo, quis tempor ligula erat
quis odio.  Nunc porta vulputate tellus.  Nunc rutrum turpis sed pede.
Curabitur lacinia pulvinar nibh.  Nam a sapien.

** aaa2

** aa3

* b
--8<---cut here---end--->8---



Re: [O] [bug/regression]: org-babel-load-file gives error: wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"

2019-01-14 Thread Gregor Zattler
Hi Kyle, org-mode developers,
* Kyle Meyer  [2019-01-14; 17:10]:
> Kyle Meyer  writes:
>> Gregor Zattler  writes:
> [...]
>
>>> I did a git bisect on the org repo and got this:
>>> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit
>>
>> Sorry, that certainly looks to be my fault (specifically, my conflict
>> resolution merging maint's d64c9a996).  I'll have a look.
>
> Fixed by baa98a4a6fe93dd99fb624ad218fb3e1868cfde3.

Thank you very much for the quick fix.  It works again.

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




[O] Paste subtree without expanding it / keep it collapsed after pasting

2019-01-14 Thread Marcelo de Moraes Serpa
Hi list,

I often copy an item and its whole subtree to move them around, I know I
can move them with the move commands, but sometimes it's faster to just
copy, paste and fix the leveling later.

I can copy or cut a collapsed subtree and it will copy everything below it
until it ends (and the next item at the same level starts), which is
intuitive and works great. However, when pasting it, it automatically
expands the tree and it makes it really hard to see the context so I can
fix the leveling, for example.

Is there a way to paste the subtree [and keep it] collapsed?

Thanks in advance!


Re: [O] [bug/regression]: org-babel-load-file gives error: wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"

2019-01-14 Thread Kyle Meyer
Kyle Meyer  writes:

> Gregor Zattler  writes:

[...]

>> I did a git bisect on the org repo and got this:
>> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit
>
> Sorry, that certainly looks to be my fault (specifically, my conflict
> resolution merging maint's d64c9a996).  I'll have a look.

Fixed by baa98a4a6fe93dd99fb624ad218fb3e1868cfde3.

-- 
Kyle



Re: [O] [bug/regression]: org-babel-load-file gives error: wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"

2019-01-14 Thread Kyle Meyer
Gregor Zattler  writes:

> Dear org-mode developers, I did a git pull half an hour ago, now I
> cannot org-babel-load-file my configuration.org any more.  Normally I
> use emacs as of git master but the (slightly different) error also
> occours with emacs 25.1.1 (as of currents debian stable) (see below).
>
> I did a git bisect on the org repo and got this:
> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit

Sorry, that certainly looks to be my fault (specifically, my conflict
resolution merging maint's d64c9a996).  I'll have a look.

-- 
Kyle



Re: [O] Bug or known issue: org-clock-display

2019-01-14 Thread Ben McGinnes
On Mon, Jan 14, 2019 at 07:56:03PM +0100, Marco Wahl wrote:
> Hi,
> 
> > no longer see the totals and org-clock-display produces the following
> > error message:
> >
> > Total file time: 0:00 (0 hours and 0 minutes)
> 
> This is the expected behavior of the org-clock-display function AFAICS.
> 
> See
> 
> C-h f org-clock-display
> 
> and
> 
> C-h v org-clock-display-default-range
> 
> The default value of org-clock-display-default-range is ‘thisyear’ which
> means that the result of
> 
> M-x org-clock-display
> 
> indeed depends on the current time.
> 
> Find also the meanings of prefix arguments for org-clock-display in
> the documentation.

Ah, cheers, this does indeed make it much more clear and changing
org-clock-display-default-range from "thisyear" to "untilnow" has
resulted in exactly what I wanted (and originally expected).  Though I
can see why it might be preferable for a default setting to run
through to the end of the current year.


Regards,
Ben


signature.asc
Description: PGP signature


Re: [O] Bug or known issue: org-clock-display

2019-01-14 Thread Marco Wahl
Hi,

> no longer see the totals and org-clock-display produces the following
> error message:
>
> Total file time: 0:00 (0 hours and 0 minutes)

This is the expected behavior of the org-clock-display function AFAICS.

See

C-h f org-clock-display

and

C-h v org-clock-display-default-range

The default value of org-clock-display-default-range is ‘thisyear’ which
means that the result of

M-x org-clock-display

indeed depends on the current time.

Find also the meanings of prefix arguments for org-clock-display in
the documentation.


HTH,  Marco





signature.asc
Description: PGP signature


Re: [O] [Patch] [Feature request] Add option to natively fontify latex snippets and environment

2019-01-14 Thread Carlos Pita
Hi Nicolas,

I was thinking that maybe it would be nicer to make this depend on the
value of org-src-fontify-natively. What do you think?

Regards
--
Carlos



[O] [bug/regression]: org-babel-load-file gives error: wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"

2019-01-14 Thread Gregor Zattler
Dear org-mode developers, I did a git pull half an hour ago, now I
cannot org-babel-load-file my configuration.org any more.  Normally I
use emacs as of git master but the (slightly different) error also
occours with emacs 25.1.1 (as of currents debian stable) (see below).

I did a git bisect on the org repo and got this:
ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit


Thanks for your attention and your work on org-mode, Gregor


emacs 251.1:
File Edit Options Buffers Tools Debugger Help   

   
Debugger entered--Lisp error: (wrong-type-argument listp 
"/home/grfz/.emacs.d/configuration.org")

  
  nth(5 "/home/grfz/.emacs.d/configuration.org")

   
  file-attribute-modification-time("/home/grfz/.emacs.d/configuration.org") 

   
  (org-file-newer-than-p tangled-file (file-attribute-modification-time file))  

   
  (if (org-file-newer-than-p tangled-file (file-attribute-modification-time 
file)) nil (org-babel-tangle-file file tangled-file "emacs-lisp"))  

   
  (let* ((tangled-file (concat (file-name-sans-extension file) ".el"))) (if 
(org-file-newer-than-p tangled-file (file-attribute-modification-time file)) 
nil (org-babel-tangle-file file tangled-file "emacs-lisp")) (if compile (progn 
(byte-$
  org-babel-load-file("/home/grfz/.emacs.d/configuration.org")  

   
  mapc(org-babel-load-file ("/home/grfz/.emacs.d/configuration.org"))   

   
  eval-buffer(# nil "/home/grfz/.emacs.d/init.el" nil t)  ; 
Reading at buffer position 7565 

   
  load-with-code-conversion("/home/grfz/.emacs.d/init.el" 
"/home/grfz/.emacs.d/init.el" t t)  

 
  load("/home/grfz/.emacs.d/init" t t)  

   
  #[0 "^H\205\266^@ \306=\203^Q^@\307^H\310Q\202?^@ 
\311=\204^^^@\307^H\312Q\202?^@\313\307\314\315#\203*^@\316\202?^@\313\307\314\317#\203>^@\320\321\322!D\nB^R\323\202?^@\316\324^S\325^A\324\211#\210^K\324=\203e^@\326\327\330\307^H\$
  command-line()

   
  normal-top-level()


emacs 27:
Debugger entered--Lisp error: (wrong-type-argument listp 
"/home/grfz/.emacs.d/configuration.org")

  
  file-attribute-modification-time("/home/grfz/.emacs.d/configuration.org") 

   
  (org-file-newer-than-p tangled-file (file-attribute-modification-time file))  

   
  (if (org-file-newer-than-p tangled-file (file-attribute-modification-time 
file)) nil (org-babel-tangle-file file tangled-file "emacs-lisp"))  

   
  (let* ((tangled-file (concat (file-name-sans-extension file) ".el"))) (if 
(org-file-newer-than-p tangled-file (file-attribute-modification-

[O] Bug or known issue: org-clock-display

2019-01-14 Thread Ben McGinnes
Hi all,
I've been using org-mode to perform the task of timesheets
with another GNU project and encountered something which has all the
hallmarks of a bug.  I'm just not sure if it's a known issue or
whether to write up a bug report for it.

I use org-clock-in and org-clock-out to track the hours worked and
then at the end of each month use org-clock-display to obtain the
total hours to bill for.

This was going fine all year until January 1st.  At this point I can
no longer see the totals and org-clock-display produces the following
error message:

Total file time: 0:00 (0 hours and 0 minutes)

If I do a find and replace of 2018 to 2019, however, the correct
calculations occur as expected.  So it appears that org-clock-display
only works for the year you're in.

BTW, the test I performed on just December, the correct total time
message is:

Total file time: 5d 22:39 (142 hours and 39 minutes)

A bit of a difference.  ;)

So, is this a known issue with possibly some arcane reason for why it
can't easily be fixed or is my next step to go lodge a formal bug
report?


Regards,
Ben



signature.asc
Description: PGP signature


[O] enhance wrap region in tables?

2019-01-14 Thread Uwe Brauer


Hi 

Please consider

#+begin_src elisp
| Title| Title |
|--+---|
| First line. First colum  | First line second column  |
| Second line. First colum | Second line, second colum |
|  |   |
#+end_src

Now when I place the cursor in the first line and at the word first
column and use the function org-table-wrap-region I obtain 

#+begin_src elisp
| Title| Title |
|--+---|
| First line.  | First line second column  |
| First colum Second line. First colum | Second line, second colum |
|  |   |
#+end_src


Couldn't I obtain 
#+begin_src elisp
| Title| Title |
|  |   |
|--+---|
| First line.  | First line second column  |
| First colum  |   |
| Second line. First colum | Second line, second colum |
|  |   |
#+end_src


Uwe Brauer