unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Org to Markdown programmatically
Date: Wed, 5 May 2021 23:11:15 +0300	[thread overview]
Message-ID: <YJL741NPiVLDyxlj@protected.localdomain> (raw)
In-Reply-To: <87sg318a6o.fsf@zoho.eu>

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-05-05 18:47]:
> >> 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.

Overall score of how, what? Where?

> >>>   (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.

I like popping.

I don't know why would the word "iterate" not relate to `while' here.

Show me how would you iterate on the above function.

When there are 2 elements to take out of the list and do something
with it, I like to pop it twice. Very handy, and why not.

Imagine if there are 3... popping thrice is so much easier than
thinking of what... I have no idea.

> Also my-keywords ... that name, also how it mixes two things,
> plus insists on a certain order without enforcing it.

You give me too much thinking here, more than it was necessary for the
function to work.

> Ever heard that once you pop you can't stop? That's what's going to
> happen, I'm afraid.

Since I have started changing `dolist' to `while' that is what
happened, there is often pop.

> > `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

Maybe I am just bored. `while' loops seem to me easier
understandable, visible. Times change.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/




  parent reply	other threads:[~2021-05-05 20:11 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YJL741NPiVLDyxlj@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).