A bunch of nice features

[maandree]

--256-colours --256colours --x-colours -X Forces uses of 256-colour ponies despite of actual terminal capabilities.

--tty-colours --ttycolours --vt-colours -V Forces used of TTY ponies (OSI P colours) despite of actual terminal capabilities.

--kms-colours --kmscolours -K Forces used of KMS ponies despite of actual terminal capabilities.

--pony-only --ponyonly -o Do not print the balloon and uses spaces instead of the link to the balloon

It may be good if the program supported the pony files to specify range of columns the balloon must cover and whether to centre around it, fill to left or fill to right.

--colour (= --colour-balloon --colour-link colour-message) --colour-balloon --colour-bubble (= --colour-balloon) --colour-link --colour-message --colour-msg (= --colour-message) --colour-pony Specify how to colour the different parts of the output. --colour-balloon=1;31 should colour the speech balloon bold red. --colour-pony will be useless, except for if the pony happens to be in ASCII art. With this you can create a script that remains you of important things. For if you have a scripted named pony-message fortune | ponysay $(pony-message) will give a fortune cookie, except if pony-message has an output. If the output is for example --colour=31 bläbb the pony will print bläbb in red with a red balloon and a red link to the balloon.

[JotaRandom]

For me the only option that I think is really missing is a ---list-all and ++list-all, that Show ALL (pony and extrapony) at same time and simlinks dependig....

[JotaRandom]

About my last comment here is a patch that add --all , -A and ++all , +A one show All (ponies AND extraponies) individually and the other show both and they alternative names

http://pastebin.com/xxgvzVrD

[svenstaro]

Make a pull request.

[JotaRandom]

I not make the pull because I not sure is work for everypony in everysystem (yours system) in my system and tests works, but at same time is my first code modification (exept my bash/zsh aliases and others)

[maandree]

If you make a pull request we can push it to the unstable branch develop and make sure it work before pushing it to master.

[JotaRandom]

er... what is the command for make a pull request from my local clone?? I know that 'git pull origin master' is from 'master' and changing 'master' line to 'develop' pull to develop right? but not sure wath is the line for "confirmation after or any"

the only problem is that I not fin a enought short description for +A/++all (list mlp:fim and non mlp:fim pony names with alternatives) se 86 of legth

[maandree]

You have permission to make changes do you do not have to do a pull request, pull requests should be done using a public server so if you do that you should update you github repo.

If you changes are in the master branch you should do the following, assuming the remote origin is this repo, and that your change is commited.

git checkout develop
git pull
git pull . master
git push -u origin develop

[JotaRandom]

ok pushed to develop (I hope on)

[maandree]

Everything here is implemented, except:

It may be good if the program supported the pony files to specify range of columns
the balloon must cover and whether to centre around it, fill to left or fill to right.

[JotaRandom]

in 2.9.1 I use util-say (dont forget update it to reflect changes) in my KMS (poulsbo/gma500_gfx yes I have that cappy graffic) the -f throw 'ponysay -f ./bonbon.png' not work and give a 1milisec message about 24color, this is normal???

[maandree]

Not to my knowledge...

util-say will need the metadata support, then I think everything is ok, but the script that generates the ttyponies uses ponysay-tool to fix that. So if I'm not overlooking anythink, the only current problem is that ponysay will not be able to generate kmsponies for ponies with metadata.

[JotaRandom]

for the kms-ponies... maybe a 3 ponydir for store them and show throw the propper 'ponysay --kmsponies pony'??, or REALLY take much time build one??

[maandree]

Building should not take much time, but the ponysay-tool --kms command is just added in case the user have a slow computer. (It is not too fun if ponysay makes your shell slow to start.)

Currently kmsponies are generated in two steps: xterm-ponies → protokmsponies → kmsponies Meaning that util-say is used two times, protokmsponies need only be made once, and kmsponies need to be made once for every TTY palette.

Before Ponysay 3.0 is complete, I'm hoping to make a new version of util-say that can do anything in one step, primarily to make the program more flexible for programming and secondarily I hope it to be faster for actions that currently need more than one step (but slower one those using just one step). It is placed that xterm-ponies should be "zebras" (looks rather good when mark in the terminals) and ttyponies and kmsponies should not be zerbra, meaning that yet another step is needed to make kmsponies with the current version of util-say.