No Wayman writes:
> Received confirmation. I will submit revisions to open patches ASAP.
I've add your name to https://orgmode.org/worg/org-contribute.html
Thanks!
--
Bastien
I am talking about this feature:
https://orgmode.org/manual/Emphasis-and-Monospace.html
It currently doesn't seem to be possible to mark a whole region with,
say, "+" to strike through a whole paragraph, especially when separating
each sentence in a paragraph by a linebreak (i believe this is
Bastien writes:
Hi,
No Wayman writes:
I assume I'll receive some sort of confirmation from FSF when
everything is processed?
Yes, you should receive a confirmation - if not within a week or
so,
let me know, sometimes asking again helps.
Best,
Received confirmation. I will submit
Budiman Snowman writes:
> Suppose I have this document:
>
> * topic1 :tag1:tag2:tag3:
> * topic2 :tag1:tag2:tag4:
> * topic3 :tag1:tag3:tag4:
> * topic4
Mario Frasca writes:
> comments on the html page org-contribute.html:
[...]
> the procedure mentioned there guides me in creating several patch files,
> one per commit. it does not describe the "squashing" you suggested me.
> I'm following your guide, but you might want to review the page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> Hi,
>
> stardiviner writes:
>
>> Here is my patch, I try to annotate on my patch code to express my
>> words:
>
> Thanks - I see what is hardcoded and why.
>
> Since the whole idea is to use something else than url-copy-file
On 3 June 2020 15:26, Nicolas Goaziou wrote:
> You only need the last `org-id-goto' call right? Is the call to this
> function meaningful, or can point be left at the beginning of "A1"
> headline instead?
Yes, I should have mentioned that you need to start in overview view.
The idea is to
Hello,
Kevin Liu writes:
> Try these commands with the following org file; it appears to fail to land on
> a heading:
>
> (org-id-goto "105dfe8b-8507-400c-862f-a25882448051")
> (org-id-goto "4a3206fc-b2f1-47d6-9876-ea30c24ecbeb")
You only need the last `org-id-goto' call right? Is the call to
Hello,
Here is a proposal for new `org-forward-paragraph' and
`org-backward-paragraph' functions, currently bound to and
. Note that functions bound to M-{ and M-} are /not/
paragraph-related functions, but we might want to reconsider it at some
point.
In any case, the purpose of this rewrite
On 03/06/2020 10:29, Bastien wrote:
The few lines above is what we called the "changelog". It should be
the first part of the commit message -- after which you can add more
free-form context and explanations, if needed.
this "Changelog", and I'm sure I am the stiffy one, isn't clear from the
consider this table, partially from the Wikipedia:
#+PLOT: with:histogram ind:1
| Region | Area | Production |Productivity |
| | (Mha) | (Mtonnes) | (tonnes/ha) |
|+++--|
| Western Europe | 2.490 | 5.730 |
If you haven't already, you probably know all about it; but, for any
newcomers on the subject of Literate Programming & source code blocks, etc.
Highly recommend Knuth's CWEB book & of course NOWEB software {which is
CWEB generalized for ALL programming languages}:
I use the config John mentioned and I like it - though I use different
symbols. Here's my config if you want an example:
https://github.com/zzamboni/dot-emacs/blob/master/init.org#source-code-blocks
--Diego
On Tue, Jun 2, 2020 at 9:24 PM John Kitchin wrote:
>
> Here is one approach:
>
>
fixing things is not as difficult as following stiff rules. anyhow,
again an attempt, with the terrible feeling I'm wasting my and your
time. (looks like I found a printer, for signing the paperwork.)
>From 3375ee101054dc087b40da119941e0433b63fea5 Mon Sep 17 00:00:00 2001
From: mfrasca
Date:
On 31 May 2020 04:09, Nicolas Goaziou wrote:
> I just fixed it, IIUC. Thank you.
It works indeed. However, I believe I have found another bug :)
Try these commands with the following org file; it appears to fail to land on a
heading:
(org-id-goto "105dfe8b-8507-400c-862f-a25882448051")
On 3 June 2020 09:27, Kevin Liu wrote:
> (org-next-previous-heading)
Typo; this should be (org-previous-visible-heading)
Mario Frasca writes:
> yes, I received the ASSIGNMENT –GNU EMACS pdf last night, I'm now
> seeing how I print & sign it. it might take some time.
Sure - probably a few weeks. Let us know when this is done so that
we can go ahead with applying your patches.
--
Bastien
Mario Frasca writes:
> I'm sure you do understand what I mean, and I guess you know what
> would be the correctly formatted version. can you show me?
Yes. You mentioned earlier that you missed this section:
https://orgmode.org/worg/org-contribute.html#commit-messages
Let me quote the text
On 03/06/2020 10:13, Bastien wrote:
Also you need to sign the FSF copyright assignment if you want to make
big changes like this one.
yes, I received the ASSIGNMENT –GNU EMACS pdf last night, I'm now seeing
how I print & sign it. it might take some time.
I'm very so much sorry Bastien, but I do not know what you mean, by "not
correctly formatted". if it were a bug report, you do agree it would be
a useless one? like "it doesn't work".
I'm sure you do understand what I mean, and I guess you know what would
be the correctly formatted version.
see attachment
>From 065ee9e35e71b0b7c0c0c2a8842909830225d962 Mon Sep 17 00:00:00 2001
From: mfrasca
Date: Tue, 2 Jun 2020 15:48:46 -0500
Subject: [PATCH] org-plot.el: adding unit tests
this patch contains some minimal refactoring for the sake of
unit-testing, and a couple of tests in the (new)
Mario Frasca writes:
> see attachment
Thanks for the effort -- the commit message is not correctly formatted
though. See https://orgmode.org/worg/org-contribute.html#commit-messages
and perhaps also read previous commit messages.
Also you need to sign the FSF copyright assignment if you want
Hi,
stardiviner writes:
> Here is my patch, I try to annotate on my patch code to express my
> words:
Thanks - I see what is hardcoded and why.
Since the whole idea is to use something else than url-copy-file for
downloading URLs I would rather add an option to allow using a custom
function.
see attachment
>From 2a30f377281955f57723ef46ff56613373cf721d Mon Sep 17 00:00:00 2001
From: mfrasca
Date: Tue, 2 Jun 2020 16:10:11 -0500
Subject: [PATCH] org-plot.el: implementing new feature "with-as-list"
Allows user specify as many `with' values as the columns in `deps'.
User can indicate
Dear Mario,
Mario Frasca writes:
> is there any mention of git-send-mail in the org-contribute guide? I
> don't see it. nor do I find hints on what to do once you have
> produced files by git-format-patch. your "send as attachment" would
> be useful there.
I added this line to
On Wed, Jun 3, 2020 at 10:40 AM Bastien wrote:
> Hi all,
>
> just a quick word in this thread to say that we are in feature freeze
> for Org core features (ie. everything in org*.el files, + ob.el/ol.el).
>
> So let's take the time to discuss this in details for 9.5 (or later,
> when it's
comments on the html page org-contribute.html:
is there any mention of git-send-mail in the org-contribute guide? I
don't see it. nor do I find hints on what to do once you have produced
files by git-format-patch. your "send as attachment" would be useful
there. or a mention of a (unix)
Hi all,
just a quick word in this thread to say that we are in feature freeze
for Org core features (ie. everything in org*.el files, + ob.el/ol.el).
So let's take the time to discuss this in details for 9.5 (or later,
when it's ready.)
Thanks!
--
Bastien
On Wednesday, 3 Jun 2020 at 21:06, Budiman Snowman wrote:
> One way I know is using a unique dedicated target, e.g.:
That's what I do in practice as it's robust to changes in headings and
is visible so I can remember the names.
You may also wish to consider CUSTOM_ID properties?
--
: Eric S
I almost always use a CUSTOM_ID property for this, e.g.
* topic1
See topic [[#topic2][topic2]].
See glossary [[#glossary_topic2][topic2]].
* topic2
:PROPERTIES:
:CUSTOM_ID: topic2
:END:
* glossary
** topic1
:PROPERTIES:
:CUSTOM_ID: glossary_topic2
:END:
** topic2
:PROPERTIES:
:CUSTOM_ID:
I have this document:
* topic1
See topic [[topic2]].
See glossary [[topic2]].
* topic2
* glossary
** topic1
** topic2
What are ways to disambiguate the internal links? The first link should
link to the topic2 first-level entry, while the second link should go to
the topic2 entry under glossary.
Hi Bastien,
On Tue, Jun 02 2020, Bastien wrote:
Hi Gustavo,
I like this idea, thanks for proposing it. We are in feature freeze
for core features, so we have time to work on this for Org 9.5.
[...]
Would you agree? Would you like to work on this change?
Well, I did give it a shot.
Suppose I have this document:
* topic1 :tag1:tag2:tag3:
* topic2 :tag1:tag2:tag4:
* topic3 :tag1:tag3:tag4:
* topic4
33 matches
Mail list logo
