RE: Recommend latex surgical gloves

RE: Recommend latex surgical gloves

[ED]

[-- Attachment #1.1: Type: text/plain, Size: 630 bytes --]

|   |
|   |
| |
|
Dear My Friend


Glad to find your email address from Google.
We supply Latex Surgical Gloves to global market.
Per my visiting your company web, I found that you have several chain store.
It is our pleasure to find a way to cooperate with you.
Quotations & Samples could be sent on request.
Any further questions, please do not hesitate to inform us.


Thanks & Regards
Ed
--

Time flies and life is short. Don’t forget to stop to smell the flowers.


YANGZHOU RUICHENG  MEDICA COMPANY
Add: Room 1310, Yatai Building, Museum Road 545#, Yangzhou, Jiangsu, China.
Skype: ed.young1227











|
| |
|   | |   |

[-- Attachment #1.2: Type: text/html, Size: 4815 bytes --]

5.0.9 / 5.1 agani (ws Re: Recommend latex surgical gloves)

[Peter Stephenson]

On Thu, 20 Aug 2015 19:15:57 +0800
ED <ed.young@ruicheng4wares.com> wrote:
> Dear My Friend
> 
> 
> Glad to find your email address from Google.
> We supply Latex Surgical Gloves to global market.

Was this a hint?

I'm hoping to make a 5.0.8-test-2 over the next few days, I hope by the
end of the weekend, to see what still needs sewing up.  Since a lot of
testing has been going on on the git archvie, which is good, I hope
that's not too much, though there's usually something when there have
been this many changes.

I'm getting bored with 5.0, since the 0 is a bit pointless, and thinking
of calling it 5.1 (no third field).  There are some quite useful bits of
enhanced compatibility here and some quite significant bug fixes.

There's nothing in the README yet about the new paste behaviour, which
there needs to be --- virtually everyone is going to run into this.  (I
know it's in NEWS but it needs to be very clear.)

(By the way, in case you're keeping count, in the source tree as a
whole, including generated docs but ignoring binaries, the score is
currently:

behaviour: 582
behavior: 169

Not sure how the disparity came about, but it may be just that I've
been overusing it myself...)

pws


diff --git a/README b/README
index 745ee6f..61af662 100644
--- a/README
+++ b/README
@@ -30,8 +30,17 @@ Zsh is a shell with lots of features.  For a list of some of these, see the
 file FEATURES, and for the latest changes see NEWS.  For more
 details, see the documentation.
 
-Incompatibilites between 5.0.8 and 5.0.9
-----------------------------------------
+Incompatibilites between 5.0.8 and 5.1
+--------------------------------------
+
+The default behaviour when text is pasted into an X Windows terminal has
+changed significantly (unless you are using a very old terminal emulator
+that doesn't support this mode).  Now, the new "bracketed paste mode"
+treats all the pasted text as literal characters.  This means, in
+particular, that a newline is simply inserted as a visible newline; you
+need to hit Return on the keyboard to execute the pasted text in one go.
+See the description of zle_bracketed_paste in the zshparams manual for
+more.
 
 As noted in NEWS, the builtins declare, export, float, integer, local,
 readonly and typeset now have corresponding reserved words that provide

Re: 5.0.9 / 5.1 agani (ws Re: Recommend latex surgical gloves)

[Bart Schaefer]

On Thu, Aug 20, 2015 at 9:42 AM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> I'm getting bored with 5.0, since the 0 is a bit pointless, and thinking
> of calling it 5.1 (no third field).

Would this mean we move away from the three-field version numbers
entirely, or would e.g. we do 5.1.1 if there were some small but
urgent fix needed (as there seems nearly always to be, as 5.0.6/7/8
demonstrated)?

> There are some quite useful bits of
> enhanced compatibility here and some quite significant bug fixes.

Yes, a surprising amount of significant progress for a short time.
Several "why didn't we think to do it this way before?" sorts of
updates.

> There's nothing in the README yet about the new paste behaviour, which
> there needs to be --- virtually everyone is going to run into this.  (I
> know it's in NEWS but it needs to be very clear.)

Is it worth mentioning how to turn it off, rather than just pointing
to the parameter doc?

> (By the way, in case you're keeping count, in the source tree as a
> whole, including generated docs but ignoring binaries, the score is
> currently:
>
> behaviour: 582
> behavior: 169

Yes, and we could probably do a similar analysis on colour and programme ...

Re: 5.0.9 / 5.1 agani (ws Re: Recommend latex surgical gloves)

[Mikael Magnusson]

On Thu, Aug 20, 2015 at 6:42 PM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
> On Thu, 20 Aug 2015 19:15:57 +0800
> ED <ed.young@ruicheng4wares.com> wrote:
>> Dear My Friend
>>
>>
>> Glad to find your email address from Google.
>> We supply Latex Surgical Gloves to global market.
>
> Was this a hint?

I have hit a snag with current git, cd no longer works. So we probably
want to hold off on the release for a bit. :)

% mkdir /tmp/ホ
% cd /tmp/ホ
cd: no such file or directory: /tmp/ホ
% cd /tmp
% cd ホ
% pwd
/tmp/ホ
% echo ホ|xxd
00000000: e383 9b0a

It doesn't happen with all japanese characters. I'm hoping one of
those bytes in the output mean something to you. I'm also assuming
this is related to the recent fudging of unmetafy in chdir().

-- 
Mikael Magnusson

mkdir builtin and $'\0'

[Oliver Kiddle]

On 21 Aug, Mikael Magnusson wrote:
> % mkdir /tmp/ホ
> % cd /tmp/ホ

While catching up on the mails, I didn't immediately spot the message
with the fix for this so instead tried to reproduce it. In the process,
I noticed an additional missing unmeta() in the fallback code used when
getcwd() returns NULL:

% rmdir $PWD
% pwd
/tmp/ャ»

Oliver

diff --git a/Src/compat.c b/Src/compat.c
index db46852..9041c0b 100644
--- a/Src/compat.c
+++ b/Src/compat.c
@@ -448,7 +448,7 @@ zgetcwd(void)
     }
 #endif /* HAVE_GETCWD */
     if (!ret)
-	ret = pwd;
+	ret = unmeta(pwd);
     if (!ret)
 	ret = dupstring(".");
     return ret;