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

> 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

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

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

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

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.

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/)]

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

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 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/)]

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

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/)]

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

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

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

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

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

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

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

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

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

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:

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

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

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

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

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/)]

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

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

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

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

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/)]

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