From: Mikael Magnusson <mikachu@gmail.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: caps strings
Date: Tue, 3 Mar 2009 18:55:30 +0100 [thread overview]
Message-ID: <237967ef0903030955l1bbe4224p9d3f4a2bf1d04c77@mail.gmail.com> (raw)
In-Reply-To: <27480.1236102218@csr.com>
2009/3/3 Peter Stephenson <pws@csr.com>:
> This should fix string arguments to functions in the caps module as
> noticed by Mikael. It looks like all the returned strings are output
> directly by library calls so aren't affected.
>
> Index: Src/Modules/cap.c
> ===================================================================
> RCS file: /cvsroot/zsh/zsh/Src/Modules/cap.c,v
> retrieving revision 1.7
> diff -u -r1.7 cap.c
> --- Src/Modules/cap.c 6 Jul 2007 21:52:40 -0000 1.7
> +++ Src/Modules/cap.c 3 Mar 2009 17:39:34 -0000
> @@ -38,6 +38,7 @@
> int ret = 0;
> cap_t caps;
> if(*argv) {
> + unmetafy(*argv, NULL);
> caps = cap_from_text(*argv);
> if(!caps) {
> zwarnnam(nam, "invalid capability string");
> @@ -90,6 +91,7 @@
> cap_t caps;
> int ret = 0;
>
> + unmetafy(*argv, NULL);
> caps = cap_from_text(*argv++);
> if(!caps) {
> zwarnnam(nam, "invalid capability string");
> @@ -97,6 +99,7 @@
> }
>
> do {
> + unmetafy(*argv, NULL);
> if(cap_set_file(*argv, caps)) {
> zwarnnam(nam, "%s: %e", *argv, errno);
> ret = 1;
I think the two zwarnnam calls with *argv needs them to be
re-metafy()ed. When i didn't do that in attr.c, I got output like
myutf8file\M-p.
--
Mikael Magnusson
next prev parent reply other threads:[~2009-03-03 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 17:43 Peter Stephenson
2009-03-03 17:55 ` Mikael Magnusson [this message]
2009-03-03 18:00 ` Mikael Magnusson
2009-03-03 18:10 ` Peter Stephenson
2009-03-03 18:21 ` Mikael Magnusson
2009-03-03 18:31 ` Peter Stephenson
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=237967ef0903030955l1bbe4224p9d3f4a2bf1d04c77@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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).