Re^5: Best way to keep script with generated output

But then you need to hardcode your own name into the file. I specifically avoided doing that. It's your call if that matters to you.

Comment on Re^5: Best way to keep script with generated output

Replies are listed 'Best First'.
Re^6: Best way to keep script with generated output by benizi (Hermit) on Dec 10, 2009 at 04:23 UTC
I don't follow. What name am I hard-coding? The `"/usr/share/X11/locale/$ENV{LANG}/Compose"` file is an input to the script. It's not the file being generated (~/.XCompose-ordering). I don't see what else is hard-coded.	[reply] [d/l]
Re^7: Best way to keep script with generated output by ikegami (Patriarch) on Dec 10, 2009 at 07:06 UTC
I'm referring to inputfile	[reply]
Re^8: Best way to keep script with generated output by benizi (Hermit) on Dec 10, 2009 at 13:27 UTC
Seems like an odd objection. For this particular task, the input will always be the same -- I just wanted to be able to run it again when that input file might change. If I were writing something where the input would change, I wouldn't have embedded the script. I would have created a script that would process a file or files, and put it somewhere proper (`~/bin` if something only useful for myself). Plus, that would defeat the initial intent of running ~/.XCompose-ordering itself to update it. Thanks for the pointers. I like what I ended up with.	[reply] [d/l]
Re^7: Best way to keep script with generated output by ikegami (Patriarch) on Dec 10, 2009 at 07:07 UTC
I'm referring to inputfile	[reply]