search for: _easily_

...there is, since Yahoo's change. As already mentioned, the "From:" field is useful as it is now (and, FWIW, I would be against changing it to something that would not easily identify the original sender, and I know I am not the only one with this opinion). If there is a way to keep _easily_ "showing" the original sender in the "From:" field/column while also complying with / adapting to Yahoo's policy, I'll welcome such solution. > We should stop for a sec and think if what yahoo did was good or not to > fight spammers; I think it was good. A l...

Hello! I tried to compile OpenSSH on my platform (BeOS), and had lots of failures due to lack of support for UNIX domain sockets, which OpenSSH seems to be using at many places. Do any of you have any ideas, or is there a working routine for _easily_ avoiding usage of such sockets (for example, by using inet domain sockets instead), while keeping the features that normally rely on them (e.g. ssh-agent)? Please note that currently I'm not on this list, so please Cc any responses to my own address. thx mortee

...Date: 01 Nov 2000 07:47:21 -0800 [...] > Thanks for the pointer to stack/unstack -- now, having been reminded, > I think I'd seen these float through on the list (still doesn't solve > the missing modeling routines (parametric GLMMs, some of the > econometrics stuff -- does R _easily_ do 3SLS?), but they'll appear > sometime, I assume). Only if someone is interested enough to write them.... Actually, I thought parametric GLMMs were an unsolved research problem in general, even in, say, the logistic case. I know there are suggestions in special cases (and there is a glm...

> From: Duncan Murdoch [snip] > For 2.1.0, would it be reasonable to extend debug() the way ? was > extended? E.g. allow > > debug(plot(x)) > > and have the debugging flag be set on the appropriate function, > whatever and wherever it happens to be? There's some ambiguity with > S3 methods (did you want to debug the generic or the method?), but I > think

...inst changing it to something that would not > easily > identify the original sender, and I know I am not the only > one with > this opinion). Yes you already said that but it's not completely clear to me why you need the author as the sender... > If there is a way to keep _easily_ "showing" >the original sender in the "From:" field/column while also > complying with / > adapting to Yahoo's policy, I'll welcome such solution. You make it sound again like yahoo implementing a "crazy" policy but I think you are just not seeing...

The comments strings in vorbis are to be 8-bit clean. info.c _v_writestring is not 8-bit clean. This leads to a malformed comment header packet if the comment has an embedded Null: 0:0 hdr2 03 76 6F 72 62 69 73 20 00 00 00 58 69 70 68 6F .vorbis ...Xipho 16:10 70 68 6F 72 75 73 20 6C 69 62 56 6F 72 62 69 73 phorus l ibVorbis 32:20 20 49 20 32 30 30 31 30 38 31 33 01 00 00

...re not looking to make a profit from your participation, you'll be sure to get some patents into the result so that you don't have to _pay_ for the result of your own labors. As a result these formats end up rife with inconsequential or even detrimental patented techniques which could have _easily_ been avoided, as essential elements. ?? and this is the outcome when all of the parties are playing by the rules. For an in-depth analysis of the mess that patents are making of standardization, see: http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1134000 It doesn't have to be this way. Mo...

Hi I had two questions regarding plots: * Is there are way to save a plot in the form of an object such that it could be displayed/modified later? * I've been using Minitab for some work and I found the burshing capability very handy (it allows me to choose a point on the graph and displays the data associated with it - x,y and other user associated data). I know that this feature is

Hi, I have only the vaguest notions of what parallel programing, but I think I have a situation where it might be of use to me, or at least provide me with the opportunity to learn more about it. Before I invest in figuring out the nuts and bolts, can anyone confirm that this is a sane approach, or provide alternatives that I could pursue? I'm running stochastic simulations, with the actual

a specification will _eventually_ be used, by someone, to tell the user they are doing things "wrong", won't it? and doesn't that turn markdown's genesis upside-down? heck, next thing you know we'll be telling them to r.t.f.m. i would prefer that implementers get more sophisticated about teasing out the user's intent in "ambiguous" cases. of course,

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be

I've been copying old passwd/shadow/group files from system to system for ages across different distributions/updates and would like to get them back in sync with each other so the system tools will work. Now they hang like: #userdel irose hangs forever, syslog says: Jul 12 11:19:32 newftp userdel[30335]: delete user `irose' Jul 12 11:19:32 newftp userdel[30335]: delete `irose'