From: Bart Schaefer <firstname.lastname@example.org> To: Zsh hackers list <email@example.com> Subject: Re: There's no xtrace output for function definitions Date: Wed, 8 Jun 2022 21:14:27 -0700 [thread overview] Message-ID: <CAH+w=7aAj7E_s2wmEVoeSEaro+ksjX47hzJdTOtbHx8tBU4kZQ@mail.gmail.com> (raw) In-Reply-To: <CAH+w=7afCwQAA1YWRkqsb4XBxX-ivA3LyT+MbKY6wYmjPSPXqQ@mail.gmail.com> On Wed, Jun 8, 2022 at 9:08 PM Bart Schaefer <firstname.lastname@example.org> wrote: > > (I hope gmail isn't actually messing up indentation > as much as I think it might be.) Sadly, it is. Back to attaching patches as txt files after this, I guess.
prev parent reply other threads:[~2022-06-09 4:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-08 16:45 Bart Schaefer 2022-06-09 4:08 ` Bart Schaefer 2022-06-09 4:14 ` Bart Schaefer [this message]
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='CAH+w=7aAj7E_s2wmEVoeSEaro+ksjX47hzJdTOtbHx8tBU4kZQ@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: There'\''s no xtrace output for function definitions' \ /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
Code repositories for project(s) associated with this 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).