specifying directory to save to or load from in speakupconf

specifying directory to save to or load from in speakupconf

[William Hubbs]

Hi Steve,

On Wed, Sep 22, 2010 at 04:48:22PM -0700, Steve Holmes wrote:
> On Wed, Sep 22, 2010 at 10:44:13AM -0500, William Hubbs wrote:
> > Speakupconf only saves or loads from /etc/speakup if it is run
> > as root, or ~/.speakup if it is run as a user.  enhancing it to allow a
> > location to be specified might be possible.
> 
> OK, I didn't remember for sure if it was hard coded or if one could
> pass a command line parm.  That change should be easy enough.  What I
> would do is if no parameters are specified, then do the current
> behavior but if a directory is specified, verify its presence and then
> use the parms from there.  I would be glad to make the change if
> people would like. Should I use the standard speakup git archive to
> pull and patch against?

Yes, just use the speakup git repository.  Make sure your clone is up to
date, then make the modification to the speakupconf script in the tools
directory.  Once you have made the changes, use 'git diff' to generate
the patch to send.

William

Re: specifying directory to save to or load from in speakupconf

[Steve Holmes]

On Thu, Sep 23, 2010 at 12:17:36PM -0500, William Hubbs wrote:
> Yes, just use the speakup git repository.  Make sure your clone is up to
> date, then make the modification to the speakupconf script in the tools
> directory.  Once you have made the changes, use 'git diff' to generate
> the patch to send.

IK, will do.  I do wonder one thing; I've usually used git
--format-patch rather than --diff.  You're preferring --diff instead?
I thought git -am's were easier to do with patches built with
format-patch.

Re: specifying directory to save to or load from in speakupconf

[William Hubbs]

On Thu, Sep 23, 2010 at 03:54:25PM -0700, Steve Holmes wrote:
> On Thu, Sep 23, 2010 at 12:17:36PM -0500, William Hubbs wrote:
> > Yes, just use the speakup git repository.  Make sure your clone is up to
> > date, then make the modification to the speakupconf script in the tools
> > directory.  Once you have made the changes, use 'git diff' to generate
> > the patch to send.
> 
> IK, will do.  I do wonder one thing; I've usually used git
> --format-patch rather than --diff.  You're preferring --diff instead?
> I thought git -am's were easier to do with patches built with
> format-patch.

In that case, you are right, use
git format-patch.

Thanks,

William

Re: specifying directory to save to or load from in speakupconf

[Steve Holmes]

Sorry, I replied to the wrong thread but for those who might be
interested, the changes talked about in this thread were recently
committed to git master so give it a shot.  My other message I just
sent goes into a bit more detail plus I updated the spkguide.txt file
with the new information.

On Thu, Sep 23, 2010 at 06:05:26PM -0500, William Hubbs wrote:
> On Thu, Sep 23, 2010 at 03:54:25PM -0700, Steve Holmes wrote:
> > On Thu, Sep 23, 2010 at 12:17:36PM -0500, William Hubbs wrote:
> > > Yes, just use the speakup git repository.  Make sure your clone is up to
> > > date, then make the modification to the speakupconf script in the tools
> > > directory.  Once you have made the changes, use 'git diff' to generate
> > > the patch to send.
> > 
> > IK, will do.  I do wonder one thing; I've usually used git
> > --format-patch rather than --diff.  You're preferring --diff instead?
> > I thought git -am's were easier to do with patches built with
> > format-patch.
> 
> In that case, you are right, use
> git format-patch.
> 
> Thanks,
> 
> William
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup