trunk/bash/sigs - can't be configured

timm / crusty

Automatically exported from code.google.com/p/crusty

0 stars 0 forks source link

trunk/bash/sigs - can't be configured #11

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

CRUSTY's random signature generator demands that everyone gets the same
quotes and name and personal details. 

Really, the core engine should be separate to the config files (but default
configs should be installed if nothing else is available).

Original issue reported on code.google.com by menzies....@gmail.com on 14 Jan 2007 at 12:13

GoogleCodeExporter commented 9 years ago

I guess proper approach is to give the user a choice for such things and then 
set
them in the appropriate config files during install.

If the user chooses not to enter anything, we do nothing and they get the 
defaults.

How does this approach sound?

Original comment by daveman1...@gmail.com on 21 Jan 2007 at 9:10

GoogleCodeExporter commented 9 years ago

I would think it'd be more appropriate to go ahead and provide the default 
files, say
sigs (the picker), sigs.quotes (the quote directory), and sigs.info (the user 
info
directory) and point the user to these files so they can be edited 
appropriately. 
Otherwise, install becomes more cumbersome than it has to be.

Original comment by bdsow...@gmail.com on 21 Jan 2007 at 9:16

GoogleCodeExporter commented 9 years ago

Why not just use signify?  Its will do exactly what your trying to do.

http://signify.sourceforge.net/

Original comment by scott.he...@gmail.com on 22 Jan 2007 at 10:38

GoogleCodeExporter commented 9 years ago

Or `fortune`.

Original comment by david.a....@gmail.com on 23 Jan 2007 at 9:35

Changed title: trunk/bash/sigs - can't be configured

GoogleCodeExporter commented 9 years ago

I think fortune is lacking in the respect that it can't include the first and 
then
randomize the rest.

Original comment by scott.he...@gmail.com on 29 Jan 2007 at 3:10