From: Mircea Damian <dmircea@linux.kappa.ro>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Cc: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-users@sunsite.auc.dk
Subject: Re: please advice
Date: Fri, 30 Jun 2000 15:21:23 +0300 [thread overview]
Message-ID: <20000630152123.G3352@linux.kappa.ro> (raw)
In-Reply-To: <001401bfe28c$fc7443c0$21c9ca95@mow.siemens.ru>; from Andrej.Borsenkow@mow.siemens.ru on Fri, Jun 30, 2000 at 04:16:14PM +0400
On Fri, Jun 30, 2000 at 04:16:14PM +0400, Andrej Borsenkow wrote:
>
> >
> > I don't see what can be wrong if I use word splitting on that
> > variable(btw,
> > word splitting is done by using WORDCHARS or just white
> > spaces?).. is there
> > somewhere an impediment for that?
> >
>
> Shell wordsplitting is using the value of IFS parameter. It should be
> compatible with current Unix standards (POSIX, XPG, SUS etc).
>
> What is the meaning of "impediment"?
uh.. sorry! I've seen that "aspell" knows it so I thought that it has the
same meaning as in my language(romanian).
It means: some reason that stays in the way of an action
To be more clear:
impediment
n 1: something immaterial that interferes with or delays action
or progress [syn: {hindrance}, {deterrent}, {handicap}]
2: anything that makes progress difficult [syn: {obstruction},
{impedimenta}]
(quote from WordNet)
--
Mircea Damian
E-mails: dmircea@kappa.ro, dmircea@roedu.net
WebPage: http://taz.mania.k.ro/~dmircea/
next prev parent reply other threads:[~2000-06-30 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-30 11:39 Sven Wischnowsky
2000-06-30 12:03 ` Mircea Damian
2000-06-30 12:16 ` Andrej Borsenkow
2000-06-30 12:21 ` Mircea Damian [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-30 12:14 Sven Wischnowsky
2000-06-30 12:17 ` Mircea Damian
2000-06-30 11:27 Mircea Damian
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=20000630152123.G3352@linux.kappa.ro \
--to=dmircea@linux.kappa.ro \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@sunsite.auc.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).