On Mon, Nov 17, 2014 at 10:54 AM, David Bjergaard dbjerga...@gmail.com wrote:
The complexity reduction is one of the benefits which I see in this.
There is also the fact that by editing `stumpwm.tex.in', sometimes it is
not clear how the manual will turn up because there is still the
November, 17 at 21:18 David Bjergaard wrote:
Diogo F. S. Ramos d...@riseup.net writes:
I know you wrote a few days ago about developing a module, I hope to
see what it is sometime soon.
Heh.
It is not a new module. And it is just a silly one.
I'm still interested :) I really need to do
I'm still interested :) I really need to do something about some of the
modules that we're hosting anyway (swm-emacs for sure). A number of
them have horrible bitrot. If your working on anything I'm very
interested to know!
It is in the Wiki.
It is a very simple module to do some primitive
Diogo F. S. Ramos d...@riseup.net writes:
Actually this would be very useful to me, I currently use a very hackish
way of controlling pulse audio's volume with these in my stumpwmrc:
(defcommand vol-up () ()
Increase the volume from the shell
(run-shell-command
pacmd set-sink-volume
Diogo F. S. Ramos d...@riseup.net writes:
I don't think the reduction in complexity will result in a
gain in productivity. If we decouple stumpwm.texi from the source,
we'll have to maintain the docstrings and the documentation. As it
stands right now, adding a function to the manual is a
Maybe we can address your concerns another way. Besides reducing
complexity (which I agree, this proposal does), was there a reason that
you felt the need to make these changes?
Reducing the complexity was not my only concern, like I stated before,
but thank you for the care.
Diogo F. S. Ramos d...@riseup.net writes:
Maybe we can address your concerns another way. Besides reducing
complexity (which I agree, this proposal does), was there a reason that
you felt the need to make these changes?
Reducing the complexity was not my only concern, like I stated before,
Reducing the complexity was not my only concern, like I stated before,
but thank you for the care.
Can you elaborate, I know that it may feel like I'm not listening, but I
feel like I'm missing a deeper point.
Oh, I didn't feel like you were not listening. I think we just disagree
about it.
I know you wrote a few days ago about developing a module, I hope to
see what it is sometime soon.
Heh.
It is not a new module. And it is just a silly one.
___
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
To generate the info manual, StumpWM first processes `stumpwm.texi.in',
scrapping the lisp source code, producing `stumpwm.texi', so it later
can be compiled by `makeinfo'.
I think we can reduce the complexity of this process by removing the
scrapping phase and separate the manual from function
10 matches
Mail list logo
