--dream is broken - it uses pwd as / (so it only works if you cd to /)

if that part is broken and you fixed it please make a patch against the original source code
the author would like to see that * and I would too and would add it to xcowsay
it will be very difficult to follow updated versions by changing official command line options
and using code snippets from the official website

doing something like this in the sources just to rename everything to xpupsay doesnt improve the code unless of course that part was broken

xcowsay can also make use of a .xcowsayrc file in the users $HOME directory. Mine now contains the following:

much easier to have some way to preset a config file

Lobster

Quote:

. . . and I have a strange feeling that the alligator in Jemimahs pond
may start talking in Fluppy

I dont know who the alligator may be in that story
but I used to live in Florida and fished in many remote places where alligators were present and very large but they keep away from people

the risks you take to go fishing you have to a fanatic

P.S Jemimah is friendly and easy to talk to so I tried out the latest Fluppy
which was the only puppy iso I had tried out since the release of puppy 4.12
as for me I have a lot of work to do building my next iso
what is most important to me is understanding how to build a distro
the simple way with packages even if it takes me along another road to set it all up
I am enjoying the walk and dont let other things distract my plan

JoeLast edited by big_bass on Sun 27 Jun 2010, 17:48; edited 1 time in total

xcowsay reads a configuration file on startup. The configuration file can be stored in the XDG compliant location $XDG_CONFIG_HOME/xcowsayrc (which will default to $HOME/.config/xcowsayrc) or in your home directory at $HOME/.xcowsayrc. If the --config=FILE command line option is passed FILE will be processed after your personal configuration file.
The configuration file consists of 'option = value' pairs, one per line. The valid keys are given in the next section. For example, the following line sets display time to 10 seconds:
display_time = 10000
The character '#' begins a comment which lasts until the end of the line.

In theory, one could have, say, five different config files for different situations: warning, error, confirmation, info, WTF#@!, and call them up with appropriate text as the second argument, or one script with a case statement that would load the appropriate one. The images could be different and appropriate for each situation.

I found the alt_image entry always resulted in the pup_small.png being used and the command line entry for image being overridden. I commented it out to allow the image I want to be display. Thanks, vovchik for the information on configuration files from the man page._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love MuchLast edited by JustGreg on Mon 28 Jun 2010, 10:30; edited 1 time in total

there is active recent development with xcowsay
so if you wanted new features or would like to suggest a patch
it would be done by the author and maintaining documented progress of the program
such as the correct way using GIT
this is the only way linux will progress in an organized way

I can't seem to get enough of a good thing. I modified your very nice but laconic xcow-repair script to use xcowsay, so that the user knows that he is doing. If there is no file dropped but just a mouse click, there is an appropriate message. This is fun

I am very blunt most of the time but I never say more than I mean or less
any attempt of trying to be eloquent for me is with much forced effort
I do agree with you 100% in my very short and to to the point way of writing
if it be code or a simple post I already feel I used too many words

Now, this is COOL!!!! You can use text attributes just as gtkdialog does with markup. The syntax is described here: http://library.gnome.org/devel/pango/stable/PangoMarkupFormat.html. It is a great little discovery. I also discovered, thanks to Lobster, that if you change the dir to /, you can use your own base image and your own dream image. This is my silly example of pretty text:

Good work Vovchik
Joe I followed up your suggestion to contact the developer
. . . coming soon new feature . . .

Quote:

Lobster to Nick Gasson:
I am the lobster from another dimension that found and suggested your program for Puppy (it has now morphed into xpupsay) I would recommend left and right sides for the image - so a Q and A type situation can be developed. Many thanks

Quote:

Nick Gasson to Lobster:
Thanks for your suggestion. It would be fairly simple to add so I'll try to include it in the next release.

I have a demo here of xcowsay speaking nicely, and showing markup. You need either festival or espeak to hear sounds. flitet sounds much worse on my machine than festival. Lobster might be interested in the routine that strips off the markup language, which I have added, so that the same text variable can be used for both sound and display. The png files and script are in the archive, as is a readme.

With kind regards,
vovchik

PS. Lobster and Joe: I have left a nice note for Nick on his site. You might want to mention to him that antialiasing of the "comment" graphics would be a nice touch, as would be 32 bbp and the full alpha channel for image display. There is quite a bit of calculation for "clouds" and rounded boxes in the source, so this might not be so easy as the suggestion regarding positioning.

1.) By the not using the standard code of xcowsy using "xpupsay"
which I admit to be very annoying but it turned out to give me a good Idea about
code conversions being able to translate code from one language to another
so in a way in the end I am thankful technosaurus changed the code or I wouldnt of had a need to change it back and then code conversion I would had missed out on
so all is well that ends well

2. the pango mark format I can see that I wrote a lot of code to make html indexes generated from bash drag n drop indexers I needed while building a website

I was working on this today editing one of my scripts to generate html code
it would be possible to make a GUI to to enter the values such as

Code:

<span foreground="blue" size="x-large">Blue text</span>

and ask forr background color , size ,text etc...

then have it generate the code using bash
pretty easily since only the GUI needs to be made I have the code to convert it
already only sight modifications were needed

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum