zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "Lawrence Velázquez" <larryv@zsh.org>,
	"Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: Does add-zle-hook-widget violate the contract of ZLE hook widgets?
Date: Tue, 29 Jun 2021 17:50:48 +0300	[thread overview]
Message-ID: <07C746D6-EA7C-4E16-BC35-7317F541D643@gmail.com> (raw)
In-Reply-To: <CAH+w=7YKGiYt5ix_QmxOkgudgMu4gkyHbhjeTPzPje6tkzv9pQ@mail.gmail.com>


> On 29 Jun 2021, at 05:06, Bart Schaefer <schaefer@brasslantern.com> wrote:
> 
> On Sun, Jun 27, 2021 at 4:19 AM Marlon Richert <marlon.richert@gmail.com> wrote:
>> 
>>> On 26 Jun 2021, at 17:52, Bart Schaefer <schaefer@brasslantern.com> wrote:
>>> 
>>> On Sat, Jun 26, 2021 at 6:14 AM Marlon Richert <marlon.richert@gmail.com> wrote:
>>>> However, my understanding of Yodl is limited. Is there a simpler way to do this?
>> 
>> Did you notice I asked a question? You left it out of your reply.
> 
> Sorry, I thought it was implicit that the simpler way is to not do it at all.
> 
> "Typically the way to do this would be to include a link to User
> Contrib within text that says something like 'see Manipulating Hook
> Functions in noderef(...)'."

OK, I see. However, since there is also an HTML version of the manual, I think adding a direct link makes a lot more sense. Also, as stated before, having an empty Utilities section makes no sense to me; documents shouldn’t have empty sections. Plus, having the subsections of Utilities listed in the menu would both make it easier to browse that page and make it easier to realize they even exist on that page in the first place. But feel free to split these two things into separate commits. I don’t think this greatly affects the text I’ve written.




  reply	other threads:[~2021-06-29 14:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27  8:19 Marlon Richert
2021-06-29  2:06 ` Bart Schaefer
2021-06-29 14:50   ` Marlon Richert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-23 20:30 Marlon Richert
2021-06-23 21:57 ` Daniel Shahaf
2021-06-23 23:33   ` Lawrence Velázquez
2021-06-24  0:09     ` Daniel Shahaf
2021-06-24 10:34   ` Marlon Richert
2021-06-24 10:45     ` Roman Perepelitsa
2021-06-24 18:54       ` Daniel Shahaf
2021-06-24 19:51         ` Roman Perepelitsa
2021-06-24 18:30     ` Daniel Shahaf
2021-06-24 21:48       ` Marlon Richert
2021-06-24 22:29         ` Lawrence Velázquez
2021-06-26 10:12           ` Marlon Richert
2021-06-26 14:51             ` Bart Schaefer
2021-06-24 23:52         ` Daniel Shahaf
2021-06-26 10:49           ` Marlon Richert
2021-06-25 17:34         ` Bart Schaefer

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=07C746D6-EA7C-4E16-BC35-7317F541D643@gmail.com \
    --to=marlon.richert@gmail.com \
    --cc=larryv@zsh.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).