Re: org-table-toggle-column-width turn on for either all tables

[Uwe Brauer]

> Uwe Brauer  writes:

> You mean shrunk? If so, there is a #+STARTUP option for that:

> #+STARTUP: shrink

Very nice, thanks precisely what I was looking for.


> I don't know of any such variable.

That is not necessary, since only column with explicit 
width options are shrunk. That is all what is needed.

|  | <18>   | <18>| |  
| 


smime.p7s
Description: S/MIME cryptographic signature

Re: org-table-toggle-column-width turn on for either all tables

[Nick Dokos]

Uwe Brauer  writes:

> Hi
>
> I find 
>
> (org-table-toggle-column-width  ARG)
>
> Very very useful, but in the current org version I have to toggle this
> for each and every table. 
>
> So I was wondering, when opening an org file 
>
> 1. Would it be possible to have all tables in an org-file have their
>column toggled.

You mean shrunk? If so, there is a #+STARTUP option for that:

#+STARTUP: shrink

>
> 2. Or with a special variable for single tables, just some of them?
>
I don't know of any such variable.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

org-table-toggle-column-width turn on for either all tables

[Uwe Brauer]

Hi

I find 

(org-table-toggle-column-width  ARG)

Very very useful, but in the current org version I have to toggle this
for each and every table. 

So I was wondering, when opening an org file 

1. Would it be possible to have all tables in an org-file have their
   column toggled.

2. Or with a special variable for single tables, just some of them?

Regards

Uwe Brauer 

Re: Bug: org-adapt-indentation is not compatible with paragraph-indent-minor-mode [9.4.5 (9.4.5-16-g94be20-elpaplus @ /home/lockywolf/.emacs.d/elpa/org-plus-contrib-20210412/)]

[Max Nikulin]

On 07/09/2021 11:02, Vladimir Nikishkin wrote:


Basically, my bug report is roughly about the subject.
`paragraph-indent-minor-mode` is shipped with Emacs by default (just like
org), and its behaviour is very standard for a lot of languages. A one
or two spaces indentation starts a new paragraph in quite a few human
languages.

However, turning on `paragraph-indent-minor-mode` seemingly disables
org's automatic indentation to the first letter of a heading, regardless
of `org-adapt-indentation` being set.


In Org syntax namely empty line serves as paragraph separator (and two 
empty lines to terminate list).


As a result of exporting of Org file it should be possible to get 
indentation instead of vertical space to represent paragraphs, however 
some tuning for each format (ascii, html, latex) will be required.


Would you expect from TeX that it should accept spaces in the beginning 
of line just as empty line for paragraph separator? Org is a markup 
format as well, so source files are not necessary should follow 
traditions of typesetting.

Re: [BUG?][PATCH] Should the `lexical-binding' variable be bound during src block with :lexical t? [9.4.6 (9.4.6-ga451f9 @ /home/n/.emacs.d/straight/build/org/)]

[No Wayman]

No Wayman  writes:


The third case I outlined.
Tangling a :lexical t src block sults in a dynamically scoped 
file unless the

user manually inserts the file-local variable line.


*results

That's adjacent to the issue I originally raised, but we could do 
better in that case.

Re: [BUG?][PATCH] Should the `lexical-binding' variable be bound during src block with :lexical t? [9.4.6 (9.4.6-ga451f9 @ /home/n/.emacs.d/straight/build/org/)]

[No Wayman]

Timothy  writes:


Hi NoWayman,


I ran into this with some code I’m writing which checks against
`lexical-binding’.
Should the following result in “lexical binding enabled” or
“lexical binding disabled”?:


Can you think of any examples where this results in different 
behaviour (without

explicitly checking `lexical-binding')?

All the best,
Timothy



The third case I outlined.
Tangling a :lexical t src block sults in a dynamically scoped file 
unless the user manually inserts the file-local variable line.

Re: Bug: Small documentation errors [9.3.6 (9.3.6-29-g6a3dff-elpaplus @ /home/jorge/.emacs.d/elpa/27.0/develop/org-plus-contrib-20200406/)]

[Jorge P . de Morais Neto]

Hi Timothy!  Thank you for the patch review and for the feedback.

Regards

-- 
- Many people hate injustice but very few check the facts.  This provokes
  misinformation.  Ask me about 
- I am Brazilian.  I hope my English is correct and I welcome feedback.
- https://www.defectivebydesign.org
- https://www.gnu.org

Re: [BUG?] org-agenda not showing entries with diary sexp timestamps

[Yuchen Pei]

Daniel Fleischer  writes:


Eric S Fraga [2021-09-10 Fri 11:57] wrote:

What works for me, for diary sexp entries, is putting the time 
in the

heading:

* 09:00-10:00 Weekly meeting
  <%%(diary-cyclic 7 9 10 2021)>



This is exactly how the feature is described in the manual:

#+begin_example
Diary-style expression entries
 For more complex date specifications, Org mode supports 
 using the
 special expression diary entries implemented in the Emacs 
 Calendar

 package(2).  For example, with optional time:

  * 22:00-23:00 The nerd meeting on every 2nd Thursday 
  of the month

<%%(diary-float t 4 2)>
#+end_example


Thanks, my bad.  I guess the reason for the time to be included in 
the headline is to be consistent with the diary format.


--
Best,
Yuchen

PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
  


signature.asc
Description: PGP signature

Re: [BUG?] org-agenda not showing entries with diary sexp timestamps

[Daniel Fleischer]

Eric S Fraga [2021-09-10 Fri 11:57] wrote:

> What works for me, for diary sexp entries, is putting the time in the
> heading:
>
> * 09:00-10:00 Weekly meeting
>   <%%(diary-cyclic 7 9 10 2021)>


This is exactly how the feature is described in the manual:

#+begin_example
Diary-style expression entries
 For more complex date specifications, Org mode supports using the
 special expression diary entries implemented in the Emacs Calendar
 package(2).  For example, with optional time:

  * 22:00-23:00 The nerd meeting on every 2nd Thursday of the month
<%%(diary-float t 4 2)>
#+end_example

-- 

Daniel Fleischer

Re: [BUG?] org-agenda not showing entries with diary sexp timestamps

[Daniel Fleischer]

Eric S Fraga  writes:

> What works for me, for diary sexp entries, is putting the time in the
> heading:
>
> * 09:00-10:00 Weekly meeting
>   <%%(diary-cyclic 7 9 10 2021)>

Actually, that is how the manual explain their usage.

[[info:org#Timestamps]]


-- 

Daniel Fleischer

Re: [BUG?] org-agenda not showing entries with diary sexp timestamps

[Eric S Fraga]

On Friday, 10 Sep 2021 at 18:00, Yuchen Pei wrote:
> Say I write the following in my agenda org file:
>
> * Weekly meeting
>  <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>

What works for me, for diary sexp entries, is putting the time in the
heading:

* 09:00-10:00 Weekly meeting
  <%%(diary-cyclic 7 9 10 2021)>

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-628-g366444
: Latest paper written in org: https://arxiv.org/abs/2106.05096

Re: [BUG?] org-agenda not showing entries with diary sexp timestamps

[Yuchen Pei]

Daniel Fleischer  writes:


Yuchen Pei [2021-09-10 Fri 18:00] wrote:


* Weekly meeting
 <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>

Invoking org-agenda with a (org-agenda-list) does not show the 
item, whereas scheduled diary sexp or plain timestamp

works fine:

* Weekly meeting
 SCHEDULED: <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>



I can reproduce; adding the hour makes the event not appear 
unless it
has a DEADLINE or SCHEDULED. 


Thanks for confirming.  The org-agenda code is not very readable 
for me with some very long functions, but I'll see if I can fix 
it.  By the way is breaking functions into smaller ones desirable 
for the project?


--
Best,
Yuchen

PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
  


signature.asc
Description: PGP signature

Re: [BUG?] org-agenda not showing entries with diary sexp timestamps

[Daniel Fleischer]

Yuchen Pei [2021-09-10 Fri 18:00] wrote:

> * Weekly meeting
>  <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>
>
> Invoking org-agenda with a (org-agenda-list) does not show the item, whereas 
> scheduled diary sexp or plain timestamp
> works fine:
>
> * Weekly meeting
>  SCHEDULED: <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>
>

I can reproduce; adding the hour makes the event not appear unless it
has a DEADLINE or SCHEDULED. 

-- 

Daniel Fleischer

[BUG?] org-agenda not showing entries with diary sexp timestamps

[Yuchen Pei]

Hello,

Can anyone reproduce this?

Say I write the following in my agenda org file:

* Weekly meeting
 <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>

Invoking org-agenda with a (org-agenda-list) does not show the 
item, whereas scheduled diary sexp or plain timestamp works fine:


* Weekly meeting
 SCHEDULED: <%%(diary-cyclic 7 9 10 2021) 9:00-10:00>

or

* Weekly meeting
 <2021-09-10 9:00-10:00 +1w>

emacs version:

GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.27, cairo version 1.17.4) of 2021-03-27


--
Best,
Yuchen

PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
  


signature.asc
Description: PGP signature

Re: [BUG?][PATCH] Should the `lexical-binding' variable be bound during src block with :lexical t? [9.4.6 (9.4.6-ga451f9 @ /home/n/.emacs.d/straight/build/org/)]

[Timothy]

Hi NoWayman,

> I ran into this with some code I’m writing which checks against
> `lexical-binding’.
> Should the following result in “lexical binding enabled” or
> “lexical binding disabled”?:

Can you think of any examples where this results in different behaviour (without
explicitly checking `lexical-binding')?

All the best,
Timothy

Re: [PATCH] Re: New source block results option for attaching file to node

[Timothy]

Hi Ryan,

I’ve just had a glance, but this looks much better to me than what was proposed
earlier . Hopefully we’ll be able to get some feedback on this from others,
and then see it merged .

All the best,
Timothy

Re: S-M-{,} on CLOCK timestamp

[Timothy]

Hi Tim,

Jorge P. de Morais Neto  writes:

> I am sorry, my description of the initial condition was incomplete.  To
> reproduce the problem, you cannot simply copy the provided text to an
> Org buffer.  You should create the clock timestamps with actual clocking
> commands.  So please do the following:

> *snip*

Have you had a chance to try reproducing this again?

All the best,
Timothy

Re: Bug: Small documentation errors [9.3.6 (9.3.6-29-g6a3dff-elpaplus @ /home/jorge/.emacs.d/elpa/27.0/develop/org-plus-contrib-20200406/)]

[Timothy]

Hi Jorge,

> [1. text/x-diff; 0001-doc-org-manual.org-Drawers-Clarify-M-TAB.patch]…

> Then how about the attached patch?  Note that I used a black star to
> indicate the position of point—the convention in the Elisp manual.
> Also, I provided a `+#+texinfo: @noindent' directive so the continuation
> would not be indented, because it is not a new paragraph.  Please tell
> whether that made sense—I know little about Texinfo and typography.

I had a look at your patch, and it seems sensible to me . I think it would be
worth merging.

> Also tell whether I am making good use of time—mine and yours.  I have
> OCD and I often nitpick about details of little relevance; feedback
> about that is always welcome.

I can’t speak for Nicolas of course, but if I may give a little feedback: IMO
improvements to the manual are always welcome — both in how easy it is to
read, and the accuracy and completeness of it. So thank you for making an effort
to improve it :)

All the best,
Timothy