From: Ihor Radchenko <yantar92@posteo.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] * lisp/org.el: (org-get-indirect-buffer) Allow indirect base buffers
Date: Sat, 05 Nov 2022 08:09:34 +0000 [thread overview]
Message-ID: <87a655lt4x.fsf@localhost> (raw)
In-Reply-To: <66cdbc7d-9720-d124-a9f1-2467ae07a4ef@alphapapa.net>
Adam Porter <adam@alphapapa.net> writes:
> The attached patch improves the function org-get-indirect-buffer, fixing
> a bug, clarifying the code, and adding a docstring.
Thanks! I have some comments.
> +(cl-defun org-get-indirect-buffer (&optional (buffer (current-buffer)) heading)
> + "Return an indirect buffer based on BUFFER.
> +If HEADING, prepend it to the name of the new buffer."
Maybe append to the name?
> + (let* ((base-buffer (or (buffer-base-buffer buffer) buffer))
> + (suffix-prefix (if heading
> + (concat heading "-")
> + ""))
Why not pre-define the whole prefix instead?
(prefix (format "%s-%s" (buffer-name base-buffer)
(if heading (concat heading "-") "")))
then, can just say (format "%s%s" prefix n) in the loop.
> + (buffer-name (cl-loop for n from 1 to 100
why to 100? It may fail (even though unlikely) and also unnecessary.
Can just say for n from 1.
> + ;; FIXME: Explain why this `condition-case' is necessary. Why
> + ;; could an error be signaled with the CLONE argument non-nil,
> + ;; and why would trying again without CLONE solve the problem?
> + (error (make-indirect-buffer base-buffer buffer-name)))))
I did not find why in the git logs. It looks like some ancient code. You
can remove it in a followup patch.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-11-05 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 19:58 [PATCH] * lisp/org.el: (org-get-indirect-buffer) Allow indirect base buffers Adam Porter
2022-11-05 8:09 ` Ihor Radchenko [this message]
2022-11-06 21:40 ` Adam Porter
2022-11-07 3:17 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a655lt4x.fsf@localhost \
--to=yantar92@posteo.net \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).