unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Platon Pronko <platon7pronko@gmail.com>
To: Joshua Lambert <jlambert.lis.tech@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Iterating over buffer lines
Date: Sat, 17 Jun 2023 08:10:33 +0800	[thread overview]
Message-ID: <c5d0c647-cd6a-ef8f-fb2e-a26dfa50cb95@gmail.com> (raw)
In-Reply-To: <CAGGu9j1jn85mAPg1bTqvtYVpNtKYFoWbmfvh3xzbP3QC=8kcjQ@mail.gmail.com>

On 2023-06-17 06:19, Joshua Lambert wrote:
> I have created some functions that make changes to one buffer line of
> a csv file. Let's call those functions a, b and c. Each of those take
> one or more arguments. I want to create a separate interactive
> function that does what function a, b, and c do, but on every line of
> the region. I successfully created a function (act-on-region-by-line)
> to go through all lines in a region and then call function a, function
> b, or function c. But, It seems redundant to have multiple functions
> that have 9-15 lines similar and one line different, the one that
> specifies function a, b or c. What is the best way to be efficient in
> this situation?
> 
> I have attempted to pass function b as a parameter, but I am slow to
> understand how to do that. Is that the best way, or is there another?
> 
> Thanks,
> J Lambert
> 

It's a bit difficult to understand what the problem is without seeing the code. Can you show the code for your latest attempt?

Yes, passing function as a parameter seems to be the best way. And partial function application might be useful here as well.

-- 
Best regards,
Platon Pronko
PGP 2A62D77A7A2CB94E




  reply	other threads:[~2023-06-17  0:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 22:19 Iterating over buffer lines Joshua Lambert
2023-06-17  0:10 ` Platon Pronko [this message]
2023-06-17  3:28   ` Joshua Lambert
2023-06-17  4:48     ` tomas
     [not found]       ` <CAGGu9j1gub_8kb92kkD30QmxLmZz8XJrwhyAPtYONE3OLe_zew@mail.gmail.com>
2023-06-17 19:17         ` tomas
2023-06-18  1:17     ` Platon Pronko

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=c5d0c647-cd6a-ef8f-fb2e-a26dfa50cb95@gmail.com \
    --to=platon7pronko@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jlambert.lis.tech@gmail.com \
    /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).