You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to play around with the awesome source and eventually contribute to the project. Do you consider awmtt an appropriate tool for testing custom awesome builds that aren't installed to the system path?
For example, I'm considering forking awmtt and adding an option to specify the path to the awesome binary. Does this seem reasonable?
The text was updated successfully, but these errors were encountered:
I haven't touched awmtt in a long while but that shouldn't be a problem. All awmtt needs is a path to the awesome binary and the configuration file. Implementation effort should be minimal.
Good for you, too. I've been wanting to contribute to Awesome in a meaningful way for quite some time, the obstacle being my pitiful C knowledge. I think 2015 might be the year ;)
I'd like to play around with the awesome source and eventually contribute to the project. Do you consider awmtt an appropriate tool for testing custom awesome builds that aren't installed to the system path?
For example, I'm considering forking awmtt and adding an option to specify the path to the awesome binary. Does this seem reasonable?
The text was updated successfully, but these errors were encountered: