unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jose A Ortega Ruiz <jao@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55879@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#55879: 29.0.50; Missing ALL argument in find-sibling-file
Date: Sat, 11 Jun 2022 14:00:11 +0100	[thread overview]
Message-ID: <87h74rz76s.fsf@mail.jao.io> (raw)
In-Reply-To: <87leu3sc03.fsf@gnus.org>

On Sat, Jun 11 2022, Lars Ingebrigtsen wrote:

> Jose A Ortega Ruiz <jao@gnu.org> writes:
>
>> Lars, perhaps it'd be a good idea to make find-sibling-file--search a
>> public function, so that it can be used from elisp? (i know it already
>> can be used, you know what i mean :))
>
> It's just a helper function for `find-sibling-file' -- do you have a use
> case for it outside of that command?

I was thinking of reusing the sibling files mechanism programmatically,
outside the mere "find a single file" scenario.  For instance, i have a
few functions that associate a list of note org files to a single pdf,
and i might want to display them all (perhaps in other window), or add
text to one of them (with the decision of which one taken
programmatically, depending on context)... For cases like that, i would
start with the result of obtaining the list of siblings inside my
commands, and find-sibling-file--search looked like the function doing
that.

Cheers,
jao
-- 
I used to think that the brain was the most wonderful organ in my
body. Then I realized who was telling me this.
  -Emo Phillips, comedian, actor





  reply	other threads:[~2022-06-11 13:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1r13xbk8d.fsf.ref@yahoo.es>
2022-06-09 21:27 ` bug#55879: 29.0.50; Missing ALL argument in find-sibling-file Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-10  5:46   ` Eli Zaretskii
2022-06-10  7:55     ` Juri Linkov
2022-06-10 10:57       ` Eli Zaretskii
2022-06-10 16:39         ` Juri Linkov
2022-06-10  9:49   ` Lars Ingebrigtsen
2022-06-10 16:18     ` Jose A Ortega Ruiz
2022-06-11 10:58       ` Lars Ingebrigtsen
2022-06-11 13:00         ` Jose A Ortega Ruiz [this message]
2022-06-11 16:09           ` Lars Ingebrigtsen
2022-06-11 21:23             ` Jose A Ortega Ruiz
2022-06-12 10:10               ` Lars Ingebrigtsen
2022-06-13  1:21                 ` Jose A Ortega Ruiz
2022-06-11 23:53             ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87h74rz76s.fsf@mail.jao.io \
    --to=jao@gnu.org \
    --cc=55879@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mardani29@yahoo.es \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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