plain list fold all top level items?

this is probably staring me in the face but i cannot seem to find in manual or help a command that will take a list - one - one sub - two - two sub - three - three sub and fold it into - one... - two... - three... without changing variables. or doing a kludge. does such a command

Specialized sparse-tree via hook to show specific view in org mode

Hi. I've been using Emacs since the 80's but I'm a new org mode user. What a fantastic piece of software. I had used my own todo mode, but org is orders of magnitude better. Thank you! My main todo file defines various TODO keywords and initial state like this: #+STARTUP: indent overview

Re: [BUG] list.orgmode.org managed to parse a message in future: 2023-10-29 [9.6.1 (release_9.6.1-223-gc8d20d @ /home/yantar92/.emacs.d/straight/build/org/)]

Jean Louis, > Why did mailing list accept message from far future? It should not be > so, that is bug to be reported. there's an old internet adage to help achieve interoperability (attributed to the late Jon Postel): be liberal in what you accept, and conservative in what you send. so, i

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

On 05/02/2023 01:59, ypuntot wrote: Then, given the time zone and the local time, you can know UTC. If orgmode gets the UTC there is not ambiguity. Mapping from local time to UTC may be ambiguous, so mapping from local time to time zone offset may be ambiguous as well. The extreme case is

Re: [BUG] list.orgmode.org managed to parse a message in future: 2023-10-29 [9.6.1 (release_9.6.1-223-gc8d20d @ /home/yantar92/.emacs.d/straight/build/org/)]

Kyle Meyer writes: > Eric replied with a patch that resolved the issue. I've installed it. Thanks! I think I saw the "future" thread disappearing briefly, but it is again there on top of https://list.orgmode.org/. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

For the Poll, the Jeans proposal would be to introduce manually: [2024-02-04 12:00 @America/Vancouver] And org to convert it into: [2024-02-04 12:00 @-08,America/Vancouver] ? Ihor's would add the option to get warnings, in case tzdata changes, when that timestamp is generated? [2024-02-04 12:00

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

* Ihor Radchenko [2023-02-05 13:45]: > [2024-02-04 12:00 @-08,America/Vancouver] will use fixed -8 offset What does that mean practically? Provide example for better understanding. - The UTC offset is not certain to remain fixed in the future. - If you do not have the time of creation of the

Re: [PATCH 0/4] Structure editing when region is active

Samuel Wales writes: > thanks for the patches. out of curiosity, does e.g. m-up m-up up deactivate? No. The patches make M-/// not deactivate. Nothing else is affected. If there are use-cases when these commands should deactivate, please share them. -- Ihor Radchenko // yantar92, Org mode

Re: [patch] improved: add TTL as defcustom to ox-icalendar

Detlef Steuer writes: > Next try. Thanks! > +Default for ~org-icalendar-ttl~ is nil. In that case the setting will > +not be used in the exported ICS file. > + > +The option may also be set using the ICAL-TTL keyword. Should quote the Org syntax keyword according to our documentation

Re: ob-sql dbconnection engine

Andreas Gerler writes: > without the patch your org source block has to look like: > > #+begin_src sql :engine mysql :dbconnection mysqldb1 > SELECT * FROM nodes; > #+end_src > > with that patch you can just type > > #+begin_src sql :dbconnection mysqldb1 > SELECT * FROM nodes; > #+end_src >

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

Ypo writes: > 4. For the Poll: What would be the expected behavior if we used the UTC > offset?  [2024-02-04 12:00 @-08,America/Vancouver] >     - We should know beforehand the DST of Vancouver, or there would be > warnings. It seems more difficult for the user: maybe the "-08," should > be

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

Samuel Wales writes: > On 2/1/23, Ihor Radchenko wrote: >> the best we can do is minimizing the breakage when designing the new syntax > > as a small nit [followup is not needed as i do not want to distract > from the big boys talking about quantum dst on pluto for timestamps > with [axial

Re: [BUG] org-manual: Using bookmarklet for org-capture is no longer reliable

Max Nikulin writes: > Likely mentioning browser extensions in the manual is the way to fix > this bug in the scope of Org. Unsure if a link to > https://chrome.google.com/webstore/ may be considered as promoting of > non-free software (Google Chrome) by a GNU project. It does not promote

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

* Ypo [2023-02-05 00:41]: > I have been thinking about how I would use this feature. So use cases > appeared, which arose some doubts about how to use this feature, and an > opinion for the Poll surged: > > If I wanted to assist to a "Mastering Emacs book club" meeting in > America/Vancouver,

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

Jean Louis writes: >> It is a correct TZ value 路 > > Time zone value? TZ environment variable value -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at

Re: netspend table

Jude DaShiell writes: > Thanks much for your help on this problem. I've never done anything with > ledger-cli yet and wasn't aware such a package existed. Glad to help :-) I now polished the tips a bit more and pushed them to my org-mode tipps:

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

* ypuntot [2023-02-04 22:01]: > Great link! > https://spin.atomicobject.com/2016/07/06/time-zones-offsets/ > > "Given a local time and an offset, you can know UTC time, but you do > not know which time zone you’re in (because multiple timezones have > the same offset)." Exactly. > So, given a

Re: [POLL] Proposed syntax for timestamps with time zone info (was: [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda)

* Ihor Radchenko [2023-02-04 13:58]: > I used "UTC+2" because it is how offsets are often represented. > For example, https://time.is/London is displaying the following: > > Time in London, United Kingdom now > ... > Time zone > - Currently Greenwich Mean Time (GMT), UTC +0 >

Re: [BUG] #+cite_export: ... bibstyle citestyle cannot be universally used as global defaults (was: Patch for \usepackage[ ... natbib = true ...]{...biblatex} with org-cite)

Dear Ihor, On Feb 4, 2023 at 12:31 PM, Ihor Radchenko wrote:Edgar Lux writes: > For example, ... the proposed idea is > a bit awkward: > > ... > #+cite_export: processor[opt1=val1,opt2=val2,...] bibliography-style[...] > citation-style[...] > > I assumed that there is one "major"