From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Org to Markdown programmatically
Date: Wed, 05 May 2021 17:36:15 +0200 [thread overview]
Message-ID: <87sg318a6o.fsf@zoho.eu> (raw)
In-Reply-To: YJKIS5S0CixSSkUP@protected.localdomain
Jean Louis wrote:
>> Oh, I found the most amazing tool - on Android of all
>> places, it was called a SEO tool but it actually went thru
>> the whole page, all aspects, even language and style, but
>> of course also the old SEO things like header-body
>> congruence and all that.
>>
>> Anyway found lots of small mistakes that I corrected. I run
>> it on all my blog post pages - and this article by far
>> scored the highest, 79%
>>
>> https://dataswamp.org/~incal/blog/box-10/marco-antonio-barrera.html
>
> Scored for which term?
Overall score.
>>> (let ((my-keywords '("TODO" hi-yellow
>>> "DONE" hi-green
>>> "URGENT" hi-red-b)))
>>> (while my-keywords
>>> (let ((keyword (pop my-keywords))
>>> (highlight (pop my-keywords)))
>>> (highlight-regexp keyword highlight)))))
>>
>> Hahaha, creative! :)
>>
>> But go get yourself a proper loop, will you :)
>
> For me, proper loops in Emacs Lisp are `while' and mapping
> functions. It gives me more clarity due to old habbits.
`while' is proper but not here as you `pop' twice in the body
when you can iterate that.
Also my-keywords ... that name, also how it mixes two things,
plus insists on a certain order without enforcing it.
Ever heard that once you pop you can't stop? That's what's
going to happen, I'm afraid.
> `dolist' and `dotimes', or cl-loop, I will never use in
> Emacs Lisp. I may use it in Common Lisp.
Sorry, but your boycott notwithstanding, they are still Elisp
functions, so actually you can't use them in CL :P
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-05-05 15:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:48 Org to Markdown programmatically Jean Louis
2021-05-04 9:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-04 10:09 ` Colin Baxter
2021-05-04 17:29 ` Jean Louis
2021-05-04 20:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 6:56 ` Jean Louis
2021-05-05 7:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 8:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 11:58 ` Jean Louis
2021-05-05 15:36 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-05-05 19:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 20:41 ` Jean Louis
2021-05-05 20:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:14 ` Jean Louis
2021-05-05 20:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-05 21:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:46 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-05 22:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 23:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 23:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-05 21:50 ` Jean Louis
2021-05-05 21:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 22:56 ` Jean Louis
2021-05-05 23:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 20:11 ` Jean Louis
2021-05-05 20:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 20:54 ` Jean Louis
2021-05-05 21:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 21:33 ` Jean Louis
2021-05-05 21:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-05 22:51 ` Jean Louis
2021-05-05 23:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-06 3:46 ` Jean Louis
2021-05-22 8:26 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg318a6o.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.