[Abcde-users] Custom Command Output to Output DIR/Folder

Roger rogerx.oss at gmail.com
Wed May 15 19:55:34 BST 2013


Another issue, if people want a TOC file written and saved to the destination 
folder (ie. $OUTPUTFILEDIR), then they also need to do so before eject (for 
ejecting the CD) is called!

I find if I create a post_move function at the forementioned line #, eject is 
already called if abcde.conf has EJECT set.  Sigh.  I think I'll implement the 
post_move function and recommend unsetting EJECT within .abcde.conf and having 
users performing eject within post_move.  (Plan to comment this within the 
submitted patch to .abcde.conf file for users.)


I should also mention, echo and printf statements were failing for some reason 
within the post_read function.  They are in my $PATH and I have also tried 
statically specifying /usr/bin/printf and /bin/echo.

I've never seen this occur when I've created Bash scripts, even extensive 
scripts.

I speculate this might occur if the abcde script redefines some internal 
variables or output mechanisms.

Another hint something is occuring, commands within the custom post_* and pre_* 
functions of .abcde.conf only shows output to stdout after EXTRAVERBOSE is set 
within .abcde.conf, but still no echo or printf stdout is seen.  Odd.

-- 
Roger
http://rogerx.freeshell.org/



More information about the Abcde-users mailing list