Currently, "Copied!" is shown even if the upload was failed actually.
It will make the user be confused.

To reproduce:

1. Make the computer offline

2. Do the following

echo hogehoge | wpbcopy

3. You will see "Copied!"

Most of the functions and variables in wpb.sh should not be called by user.
How about adding prefix them to tell them as "private" and used in wpb.

Proposals

• public variables: $WPB_ID
• private variables: $_WPB_PIPE
• public functions: wpbcopy()
  (No prefix. Also need to consider #11 )
• private functions: __wpb::spin()

They are referred from zplug.

I found a bug like this.

$ echo aaa | ttcopy
⠼ Copying... <- !!Then type Ctrl + c to interrupt the process!!

$ !!cursor is not shown!!

My suggestion about the rule related to the exit status.
How about follow the following rules AS MUCH AS POSSIBLE.

• exit command should be declared in the executable command files (in our case, ttcopy.sh or ttpaste.sh).
• Let's follow the way of numbering given by general command (like sed, grep).
• For our original purpose, let's avoid to use 1 - 2, 126 - 165, and 255.
  FYI: http://tldp.org/LDP/abs/html/exitcodes.html

For commands (ttcopy and ttpaste)

For function (like __ttcp::opts, __ttcp::is_env_ok)

終了ステータスって探しても標準的なルールなかったので、あとは決めで良いのではという気がしている。

Personally I want new features like them.

• Host1

$ echo aaa | ttcopy -i my_username -p my_password

• Host2

$ ttpaste -i my_username -p my_password
aaa

I guess, it has a chance to happen rarely due to race-condition.

from #42 by @fmyokosuka

Problems with openssl

I understood the majority.
But I can not write long sentences.
Please look at this.
↓
http://rods777.ddo.jp/~b954173/memo/ttcopy_openssl_memo_20170310.txt

For now, ttcopy post the raw URL given by transfer.sh to cl1p.net.
In order to strengthen the encryption, it is worth encrypting the URL.
As you may know, cl1p.net is only handles plain text, so base64 encoding is required.

I made develop-2.0.0 branch for #28 . I would like to resolve this issue at the same branch.

As you may know, ttcopy is depending on the curl and openssl.
It is not yet clear "Which version is already tested ?".
In addition, supported shell version is also not clear.
Any potential bugs like #42 and #45 might be discovered near future.
It is necessary to strengthen the test environment. My suggestion is following.

• Add test cases for major linux distros

  • There are tons of versions in curl and openssl. It is very troublesome if we try all the combinations between two commands. My idea is run tests on docker containers and try various linux distros.
  • all the official containers of centos https://hub.docker.com/_/centos/
  • all the official containers of ubuntu https://hub.docker.com/_/ubuntu/

• Add test cases for various bash versions.

  • I noticed that it is not necessary to test for zsh. Because shebang is #!/bin/bash. Even the current shell is in zsh, bash will be used in the ttcopy's child process.
  • I would like to set support version is 3.1 and more. (3.1 seems like PI, that's cool. 3.0 and less is too old).

No I am woking on this issue branch feature/more_test.

And generate it automatically at the first run.

It is good starting up.

I think it already has enough stuff to work at least.

Let's release it now, or let's define the issues which we have to solve before the release.

Possible solutions:

• setopt nomonitor nonotify

Excuse me.
Maybe I should create this issue more earlier...

I want to reconsider the name name of wpbcopy and wpbpaste and also the repository name.
They are not bad actually. It expresses the role of those commands well.

However, there are some concerns for me

• Difficult to type (continuous "w" and "p" keys are troublesome).
• Lazy to say (especially in Japanese: だぶりゅーぴーびーこぴー?).
  • Not catchy phrase.

How do you think about the current name of repository and command?
Once It is released, it will be very difficult to change and I want to have an opportunity to reconsider it.
if you have any ideas or candidates, let's share it here.
Off course, keeping current name is ok. it is not bad choice.

とても今更なんですが、そもそも名前どうなのってのを考えたく。。
今の名前も悪くはないんですが。

1. wcopy & wpaste
   First of all, I wondered we can use wcopy and wpaste ( Web + Copy ).
   But unfortunately, the same command is already existing( wcopy ).

2. rcopy & rpaste
   "r" means "Remote".
   Also it's existing rcopy.

3. icopy & ipaste
   "i" means "Internet".
   It does not exist, but it sounds like Apple's something...

There are three ways.

1. let user set http_proxy orhttps_proxy environment variables.

This is same as wget command.

$ export http_proxy="http://proxy.com:port/"
$ echo aaa | ttcopy # => connecting through the proxy server.

2. Support -x option

This is same as curl command.

$ echo aaa | ttcopy -x http://proxy.com:port/

3. Same as 1, but set original variable TTCP_PROXY.

Personally, I prefer 3.

• The problems of 1 is, the configuration can conflict with wget.
  • In addition, it is required to detect whether the connection is http or https. it's lazy.
• In the future, both wget and curl maybe used in order to be compatible with POSIX. The configuration for only either is better to be avoided.

I am not a believer of POSIX primitives.
However I hope all the scripts (except for testing) should be compatible with POSIX as much as possible. Because they might be used on the servers which do not have modern commands.

FYI: All the commands compatible with POSIX.
http://qiita.com/richmikan@github/items/e4cb1537d38966c10f4b

I think following changes are needed.

• Use type command instead of which.
• Abolish xmllint command and use other commands.

They are not following POSIX, but it seems too much. We need discussion.

• perl is used as sleep alternatives.
  Actually, perl is installed almost all the servers of UNIX. Even all the BSD has perl in default. If we suppose wpbcopy is used on embedded system, we should abolish it. But it is too much I think.

• curl is used to API call.
  Ideally, we should check the existence of wget, curl and fetch command and choose it. I think it is worth doing. Sometimes, newly installed linux (like docker container) does not have curl.

From tweet:
https://twitter.com/FM34311178/status/836378986850590721

### 実行環境①

[root@fmyokosuka .config]# cat /etc/redhat*
CentOS release 6.3 (Final)
[root@fmyokosuka .config]#

http://qiita.com/greymd/items/0384e961802ee593a0c2　より

手動でインストール
：
git clone https://github.com/greymd/ttcopy.git ~/ttpcopy ←これは~/ttcopyでございます。
：
~/.bashrc
source ~/ttcopy/ttcp_activate.sh
export TTCP_PROXY="http://xxxx.xxxx.co.jp:xxxx" ←これを追加しました。

そんでまず試しに同じマシンでttcopyとttpasteやってみたところ以下でした。


[root@fmyokosuka ~]# echo aaa | ttcopy
Copied!
[root@fmyokosuka ~]# ttpaste
bad decrypt
3078026988:error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length:evp_enc.c:589:

gzip: stdin: unexpected end of file
Failed to decode data.
Please check ID/Password and Salt values.
[root@fmyokosuka ~]# openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
[root@fmyokosuka ~]#

Cool stuff like

  _____   _____    ___     ___      ___  __   __ 
 |_   _| |_   _|  / __|   / _ \    | _ \ \ \ / / 
   | |     | |   | (__   | (_) |   |  _/  \ V /  
  _|_|_   _|_|_   \___|   \___/   _|_|_   _|_|_  
_|"""""|_|"""""|_|"""""|_|"""""|_| """ |_| """ | 
"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-' 

gzip command is not in the POSIX.
But I want to support it. Especially, when the delivering data is plain text, large mount of network cost can be reduced.
Let's save energy in order to save the Earth 🌏 🌍 🌎
We can save the world.
Love & Peace.

• For ttcopy: copress -> encryption -> upload

... cat | gzip | openssl aes-256-cbc -e -pass pass:$TTCP_PASSWORD ...

• For ttpaste: download -> decryption -> uncompress

... cat "$TTCP_LASTPASTE_PATH" | openssl aes-256-cbc -d -pass pass:$TTCP_PASSWORD | gzip -d

Attention:
When we finished to implement this feature, I think MAJOR version should be incremented.
Because, this feature will lost the downward compatibility (old version ttpaste cannot download the data from new version ttcopy.)

As discussed as #8, wpb.sh should put their directory into $PATH, so that the users can use the functions from other programs.

It seems bug.

# Copy
$ seq 100 | ttcopy -i aaaa -p bbbb
Copied!

# Incorrect password at first time.
$ ttpaste -i aaaa -p bbb
bad decrypt.
71168:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:/SourceCache/OpenSSL098/OpenSSL098-52.40.1/src/crypto/evp/evp_enc.c:330:
gzip: unknown compression format
Failed to decode data.
Please check ID/Password and Salt values.

# Second chance never happens.
$ ttpaste -i aaaa -p bbbb
Nothing has been copied yet.

From this tweet:
https://twitter.com/FM34311178/status/836378986850590721

### 実行環境② (WindowsにGITHUBクライアントというのをInstallしたら勝手に入ったMsys)

fmyokosuka uname -a
MINGW32_NT-6.1 fmyokosuka 2.5.0(0.295/5/3) 2016-03-31 18:26 i686 Msys
fmyokosuka
fmyokosuka git clone https://github.com/greymd/ttcopy.git ~/ttcopy
Cloning into 'C:/Users/fmyokosuka/ttcopy'...
remote: Counting objects: 615, done.
remote: Compressing objects: 100% (57/57), done.
remote: Total 615 (delta 29), reused 0 (delta 0), pack-reused 549
Receiving objects: 100% (615/615), 1.35 MiB | 413.00 KiB/s, done.
Resolving deltas: 100% (317/317), done.
Checking connectivity... done.
fmyokosuka pwd
/c/Users/fmyokosuka
fmyokosuka vi .bashrc
fmyokosuka cat ~/.bashrc
#
source ~/ttcopy/ttcp_activate.sh
export TTCP_PROXY="http://xxxx.xxxx.co.jp:xxxx"
fmyokosuka
fmyokosuka . .bashrc
fmyokosuka ttcopy
Set default ID/Password.
Enter ID for ttcopy/ttpaste: fmyokosuka
Enter password for ttcopy/ttpaste:
Enter same password again:

Created credential file '/c/Users/fmyokosuka/.config/ttcopy/config'
Execute 'ttcopy --init' to show this screen again.
fmyokosuka
fmyokosuka echo aaa | ttcopy
curl: Can't open '/proc/6848/fd/63'!
curl: try 'curl --help' or 'curl --manual' for more information
Failed to upload the content
fmyokosuka