Tim Cross writes:
> I am a little confused about the purpose of org-adapt-indentation
> though. According to the org news file, to get back the old behaviour,
> it says to explicity disable electric-indent mode using org-mode-hook.
> There is no mention of org-adapt-indentation.
Yep; as I mentio
Juri Linkov writes:
>
> What I miss in Org Babel is an equivalent of 'S-RET' that in Jupyter
> creates a new code block relative to the current code block.
'C-c C-v C-d' (org-babel-demarcate-block) splits current code block into
two with the same settings. It might be what you want. Just bind it
>> What I miss in Org Babel is an equivalent of 'S-RET' that in Jupyter
>> creates a new code block relative to the current code block.
>
> 'C-c C-v C-d' (org-babel-demarcate-block) splits current code block into
> two with the same settings. It might be what you want. Just bind it to
> something e
On 2020-11-16 Mo 06:33, Kyle Meyer wrote:
> Titus von der Malsburg writes:
>
>> Subject: [PATCH] lisp/org.el: Allow hiding #+SUBTITLE: keyword via
>> `org-hidden-keywords'
>>
>> * lisp/org.el: Allow users to include 'subtitle in
>> `org-hidden-keywords' to hide #+SUBTITLE: keyword.
>>
>> This way
First, thank your very much for suggestion.
What really I have not found your email in my Gmail (in web browser), I found it
in mu4e (Emacs). Which I can't reply because I'm in China, sendmail to Gmail
SMTP server is blocked. So I'm replying you in mu4e. Don't know whether you can
receive my mes
Daniele,
this looks good. One minor pedantic point: I think you mean
"interpreted" when you say "interpolated" (several times in the
text). Otherwise, this is a very useful addition to the manual.
Thank you,
eric
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4-107-ga0aaca.dirty
Summary: using org-clone-subtree-with-time-shift on an entry with the ID
property and a timestamp causes an error or does not create different IDs,
which worked before 27.1.
Long Description:
I have a calendar file with a lot of entries, but I slimmed it down to a MWE:
=== begin MWE ===
* my a
Summary: using org-clone-subtree-with-time-shift on an entry with the ID
property and a timestamp causes an error or does not create different IDs,
which worked before 27.1.
Long Description:
I have a calendar file with a lot of entries, but I slimmed it down to a MWE:
=== begin MWE ===
* my a
* Georges Ko [2020-11-14 11:48]:
> If I export the file as HTML, it is output as:
>
> ...
>
> so I modified org-html-link from:
>
> (concat raw-path
> "#"
> (org-publish-resolve-external-link option path t))
>
> to
>
> (concat raw-path
> "#"
> (let ((r (o
https://orgmode.org/community.html
This really needs to state that the Org-mode mailing list is
subscriber only. Membership is open, but that users should subscribe
prior to posting. The Worg page for the ML says that.
As a second request, can we get a link to Worg on the top level bar?
On 16/11/2020 11:25, Eric S Fraga wrote:
> Daniele,
>
> this looks good. One minor pedantic point: I think you mean
> "interpreted" when you say "interpolated" (several times in the
> text). Otherwise, this is a very useful addition to the manual.
Thank you for reading and for the comment.
"in
Hi Tim,
Hi All,
On Mon, 16 Nov 2020 at 18:15, Tim Cross wrote:
> Tim Cross writes:
>
>>
>> Thanks for clarifying this Kyle.
>>
>> So essentially, this change has been made to make org-mode consistent
>> with the rest of emacs which enabled electric-indent by default in Emacs
>> 24. this is a go
Hello Emacs and Org-Mode Users,
I have a question regarding the export options of org-mode.
Is there a way to toggle, whether checkboxes are exported to markdown
and plain text (ASCII buffer / file)? I did not find any on
https://orgmode.org/manual/Export-Settings.html and so far I tried the
foll
On Mon, Nov 16, 2020 at 8:43 AM Tim Cross wrote:
> So essentially, this change has been made to make org-mode consistent
> with the rest of emacs which enabled electric-indent by default in Emacs
> 24. this is a good thing. Org should be consistent with other modes. Any
> differences are likely t
> This may have consequences for
> users who are working with large PDF documents and high DPI settings who
> may not want to re-generate the PDF every time, so it may be necessary
> to make the auto reloading an option?
IMO, selecting the "...and open" option implies that you want to (re-)load th
Daniele Nicolodi writes:
> On 16/11/2020 11:25, Eric S Fraga wrote:
>> Daniele,
>>
>> this looks good. One minor pedantic point: I think you mean
>> "interpreted" when you say "interpolated" (several times in the
>> text). Otherwise, this is a very useful addition to the manual.
>
> Thank you
Hi
Lately I have deal a lot in github issues, so I thought it would be
nice to use org for this however the only package I could find seems
org-sync which is from 2012 but does not allow me to connect.
Anybody knows about a working package?
Regards
Uwe Brauer
> PS: I started to donate to org-mode a few weeks ago when I realized just
> how central it is to my workflows. If it’s the same for you, please
> join up: https://liberapay.com/bzg
> Creating reliable funding for development of essential Free Software
> tools is one of the critica
On Mon, Nov 16 2020, Uwe Brauer wrote:
> Hi
>
> Lately I have deal a lot in github issues, so I thought it would be
> nice to use org for this however the only package I could find seems
> org-sync which is from 2012 but does not allow me to connect.
>
> Anybody knows about a working package?
It
Wow, I’m impressed by your help, you are very kind!
I am also impressed by your researching skills, I gave a long go at trying
to find some code online unsuccessfully.
Yes, I agree that the agenda is a nice way to go to visualize my past
events (with v A).
My idea of not relying on the agenda inte
egin_src emacs-lisp
(add-to-list 'load-path "~/.emacs.d/elpa/org-plus-contrib-20201116")
(setq org-agenda-files '("~/test/agenda.org"))
#+end_src
- We have two files in =~/test/=: =agenda.org= and =agenda.org_archive=,
which is, as you presume, the default archi
Tim Cross writes:
> I can completely understand your position. However, I wanted to point
> out that this change was documented in the org NEWS file, where all
> version changes are documented. When upgrading to a new version of org,
> everyone should look there, ideally before the upgrade or soo
Uwe Brauer writes:
>> PS: I started to donate to org-mode a few weeks ago when I realized just
>> how central it is to my workflows. If it’s the same for you, please
>> join up: https://liberapay.com/bzg
>> Creating reliable funding for development of essential Free Software
>> t
Would it help if major releases maintained a mini-config that if added
to init.el would allow users to retain old behavior? That way they
wouldn't have to read the NEWS but could just add the relevant lines,
or maybe even just call the org-old-default-behavior-9.1 or
org-old-default-behavior-9.4. T
Here is a patch that might serve for the purpose. Best,
Tom
On Mon, Nov 16, 2020 at 5:47 AM Russell Adams wrote:
>
> https://orgmode.org/community.html
>
> This really needs to state that the Org-mode mailing list is
> subscriber only. Membership is open, but that users should subscribe
> prior t
On 11/16/2020 9:26 AM, Tom Gillespie wrote:
> Would it help if major releases maintained a mini-config that if added
> to init.el would allow users to retain old behavior? That way they
> wouldn't have to read the NEWS but could just add the relevant lines,
> or maybe even just call the org-old-def
On 11/16/2020 9:26 AM, Tom Gillespie wrote:
> Would it help if major releases maintained a mini-config that if added
> to init.el would allow users to retain old behavior? That way they
> wouldn't have to read the NEWS but could just add the relevant lines,
> or maybe even just call the org-old-def
Juri Linkov writes:
>> you can find a lot of functions like the ones in jupyter at
>> https://github.com/jkitchin/scimax/blob/master/scimax-ob.el. I setup my
>> ipython like this:
>> https://github.com/jkitchin/scimax/blob/master/scimax-org-babel-ipython-upstream.el#L89
>>
>> although I will no
Semver is unlikely to help because the question is what is "broken" by
a change in version. Semver would likely be about breaking changes to
internal org apis, not changes to default behavior that affect users,
so you have two different "semantics" which put us right back where we
are now -- to kno
Ugh, I update my emacs package pretty infrequently and I usually have 30 or
more packages updating at a time -- I can't see wading through 30 NEWS
files searching for landmines...
-- Bill
On Mon, Nov 16, 2020 at 9:10 PM Tom Gillespie wrote:
> Semver is unlikely to help because the question is
Right there with you. My primary org file has a section filled with
rage when some default gets changed in org or some other part of
Emacs. The vast majority of the time the underlying change was in the
NEWS. Since there is already a habit of updating the NEWS it doesn't
seem unreasonable to put al
Tom Gillespie writes:
> Would it help if major releases maintained a mini-config that if added
> to init.el would allow users to retain old behavior? That way they
> wouldn't have to read the NEWS but could just add the relevant lines,
> or maybe even just call the org-old-default-behavior-9.1
Alan Schmitt writes:
> Hello,
>
> I'm experimenting with a setup where each project is its own org file,
> and where I have a master file linking to active projects. How can I
> configure org to add every linked file of that master file to the
> org-agenda-files?
>
You'll probably have to write
Dr. Arne Babenhauserheide writes:
> Tim Cross writes:
>> I can completely understand your position. However, I wanted to point
>> out that this change was documented in the org NEWS file, where all
>> version changes are documented. When upgrading to a new version of org,
>> everyone should lo
Heh, I had time to read EMACS NEWS when I used it in 1985 (and still do for
new EMACS versions). Now there are s many packages, each with their own
news...
-- Bill
On Mon, Nov 16, 2020 at 10:59 PM Tim Cross wrote:
>
> Tom Gillespie writes:
>
> > Would it help if major releases maintained
Tom Gillespie writes:
> Semver is unlikely to help because the question is what is "broken" by
> a change in version. Semver would likely be about breaking changes to
> internal org apis, not changes to default behavior that affect users,
> so you have two different "semantics" which put us rig
Hi,
exporting the list example in chapter 2.6 of orgmode manual
1. The attack of the Rohirrim
2. Eowyn's fight with the witch king
+ this was already my favorite scene in the book
+ I really like Miranda Otto.
3. Peter Jackson being shot by Legolas
- on DVD only
He makes a really funn
Bill Burdick writes:
> Ugh, I update my emacs package pretty infrequently and I usually have 30 or
> more packages updating at a time -- I can't see wading through 30 NEWS
> files searching for landmines...
>
Yes, this I think is a problem. Most of those packages probably only
have minor chang
> If people don't have time to read the NEWS file, I also doubt they would
> be aware of the mini config file or have the time to add it to their
> setup. There would be an additional burden on developers to maintain the
> mini-config which might not actually result in any real benefit. I would
> a
> > Ugh, I update my emacs package pretty infrequently and I usually have 30 or
> > more packages updating at a time -- I can't see wading through 30 NEWS
> > files searching for landmines...
> >
>
> Yes, this I think is a problem. Most of those packages probably only
> have minor changes and bug f
Hello all,
I apologize in advance that this is so long.
I've been following this thread closely, because I've been using Org
mode daily for well over a decade, and this behavior affects me in
several important ways. I think this summary might be helpful.
Forever, it has been possible to start a
Tom Gillespie writes:
> Would it help if major releases maintained a mini-config that if added
> to init.el would allow users to retain old behavior? That way they
> wouldn't have to read the NEWS but could just add the relevant lines,
> or maybe even just call the org-old-default-behavior-9.1 o
Tim Cross writes:
> At the same time, us users also need to take on some of the
> responsibility and recognise that major version upgrades may break or
> change their workflow. If you have a situation where stability of your
> environment is critical to your work and your strapped for time so th
Tim Cross writes:
> There are only two mechanisms by which org-mode is upgraded and as far
> as I know, both require that the user either initiates the update or
> turns on automatic updates. Your argument would be more compelling for
> me if we were talking about updates which occur without user
Terry,
Thank you very much for the clear articulation of the problem,
it enable me to see what the issue is and find more and deeper
issues with the change.
Speaking as someone who was not affected by this change
due to the peculiarities of my config, let me say as a fairly
impartial participan
hi, Tim, et al.
i started feeling guilty yesterday, partly for being party to prolonging
this discussion (though i do think it may be important?). but also for
realizing i had *not* explored the alternatives Tim, Gustavo, and others
have suggested.
the following is *clearly* the department of ir
Titus von der Malsburg writes:
> Updated patch attached.
Thanks. Applied (8bade78ce).
Gerardo Moro writes:
> Hi,
>
> I want my agenda to have follow-mode active when starting Emacs.
> I suppose this would do the trick?
>
> (setq org-agenda-start-with-follow-mode t)
> (setq org-agenda-follow-indirect t)
>
> 1) Do I need both? I have observed that having only the second one does not
At 2020-11-17 12:52:06, "Kyle Meyer" wrote:
>Gerardo Moro writes:
>
>> Hi,
>>
>> I want my agenda to have follow-mode active when starting Emacs.
>> I suppose this would do the trick?
>>
>> (setq org-agenda-start-with-follow-mode t)
>> (setq org-agenda-follow-indirect t)
>>
>> 1)
Good work Greg.
My only comment is about the tests in src blocks. I'm not sure about these
as I always use the special editing mode for source blocks and I would
expect that when you do this, the editing buffer would adopt the semantics
of the native mode for the source language being edited. (I h
Gustavo Barros writes:
> Hi All,
>
> The toggling of Archives mode in the agenda, the one which includes
> archive files, called with "v A", can be turned on, but turning it off
> with "v A" does not currently work.
>
>
> An ECM to reproduce the issue is:
Thanks for the report and reproducer.
* stardiviner [2020-11-16 13:21]:
:PROPERTIES:
:ID: e2c30814-b983-4391-869a-3c700d041467
:END:
>
> First, thank your very much for suggestion.
>
> What really I have not found your email in my Gmail (in web
> browser),
Maybe because it went to Spam/Junk folder. For privacy and safety
reas
Tom Gillespie writes:
> with upstream, but it is clear that upstream has done zero testing on
> the impact of that change on org-mode (or any other mode for that matter).
I think this statement is too hard. If you use org purely for the
example usecase (headings with a single content-line) and u
>>> "TC" == Toon Claes writes:
> On Mon, Nov 16 2020, Uwe Brauer wrote:
>> Hi
>>
>> Lately I have deal a lot in github issues, so I thought it would be
>> nice to use org for this however the only package I could find seems
>> org-sync which is from 2012 but does not allow me to connect.
>>
>>
On Mon, 16 Nov 2020 16:24:45 -0700, T.F. Torrey wrote:
[...]
> The proper fix for this is one of two choices:
>
> 1. If keeping electric-indent-mode on is really important, the easiest
>way to restore intuitive behavior is to change the default of
>org-adapt-indentation to nil. Yes, this
Hello Nick,
On 2020-11-16 16:33, Nick Dokos writes:
> Just guessing at this point, I would imagine you'd want something like
> this:
>
> --8<---cut here---start->8---
> (defun path-from-link (link)
>(org-element-property :path link))
>
> (setq org-agenda-f
56 matches
Mail list logo
