zsh-users
 help / color / mirror / code / Atom feed
From: Wataru Kagawa <wkagawa@jota.gsc.riken.go.jp>
To: zsh-users@sunsite.dk
Subject: Re: joining array elements
Date: Thu, 12 Jan 2006 14:17:44 +0900	[thread overview]
Message-ID: <A61FA50A-E761-49CC-B86C-206C54A8AE61@jota.gsc.riken.go.jp> (raw)
In-Reply-To: <6DC50D24-618F-4531-BA06-0F31570283C1@jota.gsc.riken.go.jp>

I noticed that to get the joining to work, I have to unset the  
'globsubst' option.

Wataru Kagawa


On 2006/01/12, at 10:59, Wataru Kagawa wrote:

> Hi Bart,
>
> When I removed the backslashes, I have no output.  Could this  
> problem be related to the Zsh options I have set in my  
> environment?  I have the following options set (or unset).
>
> 	setopt                         \
> 			auto_pushd             \
> 		 NO_beep                   \
> 			brace_ccl              \
> 		 NO_cdable_vars            \
> 		 NO_clobber                \
> 			complete_in_word       \
> 			correct_all            \
> 			extended_glob          \
> 			glob_complete          \
> 			glob_subst             \
> 			hist_allow_clobber     \
> 			hist_reduce_blanks     \
> 		 NO_hup                    \
> 			ignore_eof             \
> 			interactive_comments   \
> 		 NO_list_ambiguous         \
> 			local_options          \
> 			local_traps            \
> 			long_list_jobs         \
> 			magic_equal_subst      \
> 			null_glob              \
> 			path_dirs              \
> 			posix_builtins         \
> 			print_eight_bit        \
> 			pushd_ignore_dups      \
> 			pushd_minus            \
> 			pushd_to_home          \
> 			rc_expand_param        \
> 		 NO_sh_in_stdin            \
> 			share_history          \
>
>
> I appreciate your help very much.
>
> Wataru Kagawa
>
>
> On 2006/01/12, at 10:41, Bart Schaefer wrote:
>
>> On Jan 12, 10:22am, Wataru Kagawa wrote:
>> }
>> } Bob[return]Sara[return]Tim
>> }
>> } as an output (without the backslashes in front of the square
>> } brackets).  I started out with,
>> }
>> } echo ${(j:\[return\]:)usernames}
>> }
>> } and added extra backslashes, but that did not work for me.  Help is
>> } greatly appreciated.
>>
>> Did you try *removing* the backslashes?  This works fine for me:
>>
>> echo ${(j:[return]:)usernames}
>>
>> Also keep in mind that "echo" might be doing some conversions of its
>> own if you have anything unusual in $usernames -- you might be better
>> off with e.g.
>>
>> print -R -- ${(j:[return]:)usernames}
>


  reply	other threads:[~2006-01-12  5:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  1:22 Wataru Kagawa
2006-01-12  1:41 ` Bart Schaefer
2006-01-12  1:59   ` Wataru Kagawa
2006-01-12  5:17     ` Wataru Kagawa [this message]
2006-01-12  9:10       ` Peter Stephenson
2006-01-12 11:44         ` Wataru Kagawa
2006-01-12 11:54           ` Peter Stephenson
2006-01-12 12:20             ` Wataru Kagawa
     [not found]               ` <10756.1137069559@logicacmg.com>
2006-01-12 13:01                 ` Wataru Kagawa
2006-01-12 13:10               ` Peter Stephenson
2006-01-12 15:16                 ` Wataru Kagawa

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=A61FA50A-E761-49CC-B86C-206C54A8AE61@jota.gsc.riken.go.jp \
    --to=wkagawa@jota.gsc.riken.go.jp \
    --cc=zsh-users@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).