Hi,

In this version of the org-mode manual in the current repo, there are three capture template properties (shown in the source) which are not documented:

:jump-to-captured
:empty-lines-before
:empty-lines-after

I hope that these can be added in time for v. 9.4

Best,

Ian




On Sat, Jun 20, 2020 at 12:02 PM <emacs-orgmode-request@gnu.org> wrote:
Send Emacs-orgmode mailing list submissions to
        emacs-orgmode@gnu.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/emacs-orgmode
or, via email, send a message with subject or body 'help' to
        emacs-orgmode-request@gnu.org

You can reach the person managing the list at
        emacs-orgmode-owner@gnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Emacs-orgmode digest..."


Today's Topics:

   1. Re: New mailing list archive at https://orgmode/list/
      (Eric Abrahamsen)
   2. [FR] Add check for attachments in org-lint (Gustavo Barros)
   3. [Feature request] toggle inline image display only under
      current subtree (stardiviner)
   4. Re: Get Grades Done: the joys of Org's simple power
      (Richard Lawrence)
   5. Re: Anyone doing any fancy customizations of source blocks?
      (Diego Zamboni)
   6. [Manual] missing parameter documentation in the Capturing
      column view paragraph (Paul Bonaud)
   7. Re: [Manual] missing parameter documentation in the Capturing
      column view paragraph (Kyle Meyer)
   8. patch: ob-clojure improvements (Ag Ibragimov)
   9. Re: patch: ob-clojure improvements (stardiviner)
  10. org-mode as a logging target in three easy steps (Meng Weng Wong)
  11. texinfo manual links not working? (Leo Alekseyev)
  12. Re: texinfo manual links not working? (Nicolas Goaziou)


----------------------------------------------------------------------

Message: 1
Date: Fri, 19 Jun 2020 10:37:01 -0700
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eric Wong <e@yhbt.net>
Cc: Kyle Meyer <kyle@kyleam.com>,  emacs-orgmode@gnu.org
Subject: Re: New mailing list archive at https://orgmode/list/
Message-ID
: <875zbn554y.fsf@ericabrahamsen.net>
Content-Type: text/plain; charset="utf-8"

Eric Wong <e@yhbt.net> writes:

> Kyle Meyer <kyle@kyleam.com> wrote:
>> Eric Abrahamsen writes:
>>
>> > Hey, that works great! It's a bit weird that it still asks for a
>> > username and password, I wonder if there's any way to skip that. I've
>> > never dealt with anonymous IMAP before -- is there anything in the
>> > connection process that explicitly tells us "you don't need to log on"?
>>
>> The server advertises AUTH=ANONYMOUS as a capability [*], so Gnus could
>> detect that and send "AUTHENTICATE ANONYMOUS", I _think_.
>
> Fwiw, mutt detects AUTH=ANONYMOUS and uses it automatically,
> so I think it's reasonable for Gnus and others do the same.

Looks like it would be as simple as the attached diff. I have very
little confidence in my understanding of the potential ramifications,
though, so I'll open an Emacs bug and see what other people think.

Eric

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nnimap-anonymous.diff
Type: text/x-patch
Size: 1140 bytes
Desc: not available
URL: <https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20200619/16079c41/attachment.bin>

------------------------------

Message: 2
Date: Fri, 19 Jun 2020 15:43:15 -0300
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [FR] Add check for attachments in org-lint
Message-ID: <878sgi522l.fsf@gmail.com>
Content-Type: text/plain; format=flowed

Hi All,

Org 'attachment:' links are essentially file links to local files and,
while 'org-lint' checks 'file:' links for the existence of the
corresponding files with `org-lint-link-to-local-file', as far as I can
tell, the same check is not done for 'attachment:' links.

So, I'd like to kindly suggest that either "attachment" be included as a
case in `org-lint-link-to-local-file' or that an equivalent check for
attachments be included in `org-lint'.  I'd be much thankful.

Best,
Gustavo.



------------------------------

Message: 3
Date: Sat, 20 Jun 2020 10:25:28 +0800
From: stardiviner <numbchild@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: [Feature request] toggle inline image display only under
        current subtree
Message-ID: <87wo42lbhj.fsf@gmail.com>
Content-Type: text/plain


For some Org documents which has lots of images, toggle display of all inline
images will suspend Emacs, and use lot of memory. I suggest Org Mode can add an
[C-u] universal prefix detect before [C-c C-x C-v] to only display inline images
under subtree.

WDYT?

--
[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3



------------------------------

Message: 4
Date: Sat, 20 Jun 2020 06:10:03 +0200
From: Richard Lawrence <wyley.r@gmail.com>
To: Devin Prater <r.d.t.prater@gmail.com>
Cc: Phil Regier <phil.regier@gmail.com>, emacs-orgmode
        <emacs-orgmode@gnu.org>
Subject: Re: Get Grades Done: the joys of Org's simple power
Message-ID: <87pn9ubco4.fsf@aquinas>
Content-Type: text/plain; charset=utf-8

Hi Devin,

Devin Prater <r.d.t.prater@gmail.com> writes:

> Ah, I’m using Safari on MacOS 10.15. I can try with Chrome as well, though.

Did it work in Chrome, and/or when you moved the script to the end of
the file?

For what it's worth, here is a new version that should work better
regardless of where it's placed in the document.  The only change is
that the code which replaces the text representation of the checkboxes
with HTML checkboxes has been wrapped in a function that fires on the
"DOMContentLoaded" event.

Hope that's helpful!

--
Best,
Richard

#+begin_export html
<script type="text/javascript">
  function updateCookiesIn(div) {
      const headline = div.querySelector("h1, h2, h3, h4, h5, h6");
      if (!headline) return;
      const cookies = Array.from(headline.querySelectorAll("code"))
            .filter(c => c.innerText.startsWith("[") && c.innerText.endsWith("]"));
      const fracCookies = cookies.filter(c => c.innerText.includes("/"));
      const pctCookies = cookies.filter(c => c.innerText.includes("%"));

      // The ugly query strings here restrict the selection to checkboxes at *this* level of the hierarchy
      const allTasks = div.querySelectorAll(`#${div.id} > div > ul input[type=checkbox], #${div.id} > div > ol input[type=checkbox]`);
      const completedTasks = div.querySelectorAll(`#${div.id} > div > ul input[type=checkbox]:checked, #${div.id} > div > ol input[type=checkbox]:checked`);

      const newFrac = `[${completedTasks.length}/${allTasks.length}]`;
      const newPctText = allTasks.length
            ? (100 * completedTasks.length / allTasks.length).toFixed(0)
            : "100"; // Org shows 100% for a cookie when there are no checkboxes
      const newPct = `[${newPctText}%]`;

      fracCookies.forEach(c => c.innerText = newFrac);
      pctCookies.forEach(c => c.innerText = newPct);
  }

  function replaceWithCheckbox(code) {
      const isChecked = code.innerText.includes("X");

      const checkbox = document.createElement("input");
      checkbox.setAttribute("type", "checkbox");
      if (isChecked) checkbox.setAttribute("checked", "checked");
      checkbox.onclick = function (e) {
          const container = findContainingSection(e.target);
          if (!container) return;
          updateCookiesIn(container);
      };

      code.replaceWith(checkbox);
  }

  function findContainingSection(el) {
      if (!el.parentElement) return null;

      const parent = el.parentElement;
      const classes = Array.from(parent.classList);
      if (classes.some(cl => cl.startsWith("outline") && !cl.startsWith("outline-text"))) {
          return parent;
      } else {
          return findContainingSection(parent);
      }
  }

document.addEventListener("DOMContentLoaded", function(event) {
  const orgCheckboxes = document.querySelectorAll(".off > code, .on > code");
  orgCheckboxes.forEach(replaceWithCheckbox);

  const orgSections = document.querySelectorAll("div.outline-1, div.outline-2, div.outline-3, div.outline-4, div.outline-5, div.outline-6");
  orgSections.forEach(updateCookiesIn);
});

</script>
#+end_export



------------------------------

Message: 5
Date: Fri, 19 Jun 2020 07:19:48 +0000
From: Diego Zamboni <diego.zamboni@hey.com>
To: William Denton <wtd@pobox.com>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Anyone doing any fancy customizations of source blocks?
Message-ID: <92d795d6815b65c332aaf30c262bcbbebf6182bd@hey.com>
Content-Type: text/plain; charset="utf-8"

Hi Bill,

I'm glad you found the example useful. I've been thinking myself of also un-hiding the header arguments, which I do find useful to have visible.

Best,
--Diego
On Fri, Jun 19, 2020 at 4:04 AM William Denton <wtd@pobox.com> wrote:
“On 3 June 2020, Diego Zamboni wrote:

> 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

Thanks for this. I used it for a while, and it looks great, but I decided I 
want to see the details on the begin_src line all the time. I do like using the 
⎡and ⎣ character nr prettify-symbols-ali stto replace #+begin_src and 
#+end_src and will keep those.

(My apologies for weirdness in that line---the Unicode threw things off and 
I can't get it back to normal.)

I'll refer to your configuration file when I move my init files into Org. It's 
a great example.

Bill
--
William Denton :: Toronto, Canada --- Listening to Art: https://listeningtoart.org/
https://www.miskatonic.org/ --- GHG.EARTH: https://ghg.earth/
Caveat lector. --- STAPLR: https://staplr.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20200619/e44fd894/attachment.html>

------------------------------

Message: 6
Date: Fri, 19 Jun 2020 21:03:05 +0200
From: Paul Bonaud <paul@bonaud.fr>
To: emacs-orgmode@gnu.org
Subject: [Manual] missing parameter documentation in the Capturing
        column view paragraph
Message-ID:
        <CAE8rFStOqq4nt1XFnYYi+nXgkojtwi1HYFYu78DgheF50VjETg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello,

In the “Capturing column view” paragraph of the Org-mode manual there is no
mention of the `:match` parameter which was added in
https://code.orgmode.org/bzg/org-mode/commit/8983ac917b1ca1b46697a5d27655e4ef71fa6537

It would be nice to add it in the Manual of org-mode available at
https://orgmode.org/manual/Capturing-column-view.html

If I can contribute via a patch or git please let me know how I can do
this. I didn't find the source code of the orgmode.org/manual in the wild.

Many thanks for your help and have a nice day,
Paul B.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20200619/c7dc6ab9/attachment.html>

------------------------------

Message: 7
Date: Sat, 20 Jun 2020 05:44:02 +0000
From: Kyle Meyer <kyle@kyleam.com>
To: Paul Bonaud <paul@bonaud.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Manual] missing parameter documentation in the Capturing
        column view paragraph
Message-ID: <87mu4yb8bh.fsf@kyleam.com>
Content-Type: text/plain; charset=utf-8

Paul Bonaud writes:

> In the “Capturing column view” paragraph of the Org-mode manual there is no
> mention of the `:match` parameter which was added in
> https://code.orgmode.org/bzg/org-mode/commit/8983ac917b1ca1b46697a5d27655e4ef71fa6537
>
> It would be nice to add it in the Manual of org-mode available at
> https://orgmode.org/manual/Capturing-column-view.html

Thanks for noticing.  It looks like an entry for :match was added by
Carsten in 1a978953a (2020-03-23).  That commit will be included in the
9.4 release.

> If I can contribute via a patch or git please let me know how I can do
> this. I didn't find the source code of the orgmode.org/manual in the wild.

For future reference, it's in the above repo under doc/org-manual.org.
Patches for other issues are of course very appreciated.  Information on
contributing is at <https://orgmode.org/worg/org-contribute.html>.



------------------------------

Message: 8
Date: Fri, 19 Jun 2020 23:55:48 -0700
From: Ag Ibragimov <agzam.ibragimov@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: patch: ob-clojure improvements
Message-ID: <m2y2oimdjf.fsf@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi everyone, here's my attempt to add clojure CLI and babashka support for ob-clojure.el

- Adds a header parameter to override org-babel-clojure-backend
- Adds :args param (right now only used for clojure-cli)

I have tested it with these minimal cases:

#+begin_src clojure :backend clj-cli :args "-Sdeps '{:deps {inflections {:mvn/version \"0.13.2\"}}}'"
  (use 'inflections.core)
  (plural "word")
#+end_src

#+begin_src clojure :backend babashka :results output
  (range 10)
#+end_src

Please let me know what you think. Any advice is appreciated, since I have never contributed before. Thank you.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ob-clojure-improvements.patch
Type: text/x-patch
Size: 3538 bytes
Desc: not available
URL: <https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20200619/79753daf/attachment.bin>

------------------------------

Message: 9
Date: Sat, 20 Jun 2020 16:23:48 +0800
From: stardiviner <numbchild@gmail.com>
To: Ag Ibragimov <agzam.ibragimov@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: patch: ob-clojure improvements
Message-ID: <874kr6402z.fsf@gmail.com>
Content-Type: text/plain


Glad to see your patch, really useful in some cases. Thanks.

Ag Ibragimov <agzam.ibragimov@gmail.com> writes:

> Hi everyone, here's my attempt to add clojure CLI and babashka support for ob-clojure.el
>
> - Adds a header parameter to override org-babel-clojure-backend
> - Adds :args param (right now only used for clojure-cli)
>
> I have tested it with these minimal cases:
>
> #+begin_src clojure :backend clj-cli :args "-Sdeps '{:deps {inflections {:mvn/version \"0.13.2\"}}}'"
>   (use 'inflections.core)
>   (plural "word")
> #+end_src
>
> #+begin_src clojure :backend babashka :results output
>   (range 10)
> #+end_src
>
> Please let me know what you think. Any advice is appreciated, since I have never contributed before. Thank you.


--
[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3



------------------------------

Message: 10
Date: Sat, 20 Jun 2020 17:52:00 +0800
From: Meng Weng Wong <mengwong@gmail.com>
To: emacs-orgmode@gnu.org
Subject: org-mode as a logging target in three easy steps
Message-ID:
        <CA+r+iygnFjKv0+jy4poZXmLrbQ51TTmshNN_j8Yc=VsjBLjiTA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I've been enjoying a featherweight alternative to log levels, made possible
by org-mode. I've done this a couple of times now and am feeling good
enough about it to recommend it to others.

The next time you write a little throwaway script:

Step 1: Add asterisks to the front of your printf traces.

Step 2: Tee your STDOUT / STDERR to a file named log.org

Step 3: Open the log file in org-mode.

Step 4: Enjoy!

This illustration uses a Github scraper as an example:
https://github.com/mengwong/git-scrape
https://twitter.com/mengwong/status/1274236595109982208

This is no substitute for real structured logging, of course :)

You can tail the logfile with M-x auto-revert-mode.

That is all!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20200620/d5a083ca/attachment.html>

------------------------------

Message: 11
Date: Sat, 20 Jun 2020 03:51:13 -0700
From: Leo Alekseyev <dnquark@gmail.com>
To: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: texinfo manual links not working?
Message-ID:
        <CADzxs1kQiG1VoOcZ6LoVfN00D=rhHUuKRb6jAOJT06F4C_kpMw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

M-x org-store-link tells me "No method for storing a link from this
buffer", and info: type is not in the list when I try to insert a link
via C-c C-l. Has the support been deprecated or is there a problem
with my system?



------------------------------

Message: 12
Date: Sat, 20 Jun 2020 13:16:29 +0200
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: Re: texinfo manual links not working?
Message-ID: <87o8peyoky.fsf@nicolasgoaziou.fr>
Content-Type: text/plain

Hello,

Leo Alekseyev <dnquark@gmail.com> writes:

> M-x org-store-link tells me "No method for storing a link from this
> buffer", and info: type is not in the list when I try to insert a link
> via C-c C-l. Has the support been deprecated or is there a problem
> with my system?

I think you need to (require 'ol-info)

Regards,

--
Nicolas Goaziou



End of Emacs-orgmode Digest, Vol 172, Issue 21
**********************************************


--
=====
Ian Garmaise
Consultant
Phorix Solutions Group
ian.g@phorixsol.com
Toronto cell: 416.432.2251
NYC: 917.512.9535

https://www.linkedin.com/in/igarmaise/

http://www.PhorixSol.com