Re: Matchbox 0.5rc1
Matthew Allum <[email protected]>
| Newsgroups | gmane.comp.handhelds.matchbox |
|---|---|
| Message-ID | <20030404220944.GA24198@debian> |
on Fri, Apr 04, 2003 at 02:59:39PM -0500, Ty Sarna wrote: > Yay! And looks like you already did the rest of my wishlist in 0.5. > Though I have come up with a new wishlist item: the ability to > programatically launch/pop-to-front a monolaunch. Perhaps an option that > would tell it to write a pid file, and the have kill -HUP or -USR1 or > something on the pid simulate a button push. > > This is good if you want bootup/login/whatever to come up with an app > already running, but you want a click on it's button to pop it to front > again instead of staring a second copy. > Im sorry but Im not sure what you mean - you want to start an app automatically ( in your .xinitrc or whatever ), but have monolaunch be able to hide/show it aswell ? > > BTW, I started working on NetBSD package for 0.5. Looks like some of > the build issues I ran into with 0.4 are already fixed. One of the > remaining issues is that NetBSD doesn't have strndup. After > investigating this function, I consider this a good thing, as nobody > even among the Linux people can seem to agree on what the semantics > are... does it: > > allocate N and strncpy? > allocate N and strlcpy? > allocate N+1 and strncpy or memcpy and add \0? > allocate as much as needed, but at most n and strncpy? > allocate as much as needed, but at most n and strlcpy? > allocate as much as needed, but at most n+1 and add \0? > > and my favorite: > > have comments describing one of the variants above, but > code that tries to implement another, but with bugs. > > (It's left as an excersize to the reader to google around and see who > implements what variant -- I count versions implementing at least 3 of > the above.) > > My suggestion is to figure out what semantics you actually need, write a > new function with a new name that implements them, and use that. strndup > should be avoided until people can agree on what the hell it actually > does, IMHO :-) Yep, no problem - its only called a couple of times. Consider it removed for the next rc / 0.5 full release. Any other netBSD issues ? -- Matthew