From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: Clarify check-for-changes with mercurial
Date: Sat, 07 May 2011 10:09:04 -0700 [thread overview]
Message-ID: <110507100907.ZM22611@torch.brasslantern.com> (raw)
In-Reply-To: <110507095711.ZM22549@torch.brasslantern.com>
On May 7, 9:57am, Bart Schaefer wrote:
}
} yodl'd into "info" format, var(xxx) gets rendered into all-caps XXX
} (possibly depending on what info viewer is used).
As an example of this, when I view the vcs_info documentation I see
this kind of thing:
****
26.4.2 Configuration
--------------------
The VCS_INFO feature can be configured via ZSTYLE.
****
I'm pretty sure those weren't intended to be capitalized.
--
next prev parent reply other threads:[~2011-05-07 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 6:49 Frank Terbeck
2011-05-07 16:57 ` Bart Schaefer
2011-05-07 17:09 ` Bart Schaefer [this message]
2011-05-07 17:12 ` Frank Terbeck
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=110507100907.ZM22611@torch.brasslantern.com \
--to=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).