I had three Lifestyle Lifts and now have more confidence than ever. I look good, feel confident, and just landed a new high-paying job. I don't know why the government is giving them a hard time. Don't they have something else to do, like fight crime or win wars or something?
Matter duplication is a tricky problem. Assembling the integral units is already an issue. 3D printers carve matter out of chalk, cardboard, or wax, not a chunk of metal necessary for transmitting energy from the front to the back of a car.
We have the ability to fabricate a plan into a gear or another hunk of metal. Push the AutoCAD specs into a fab. We, as in humanity, also have used robots to assemble those fabricated hunks into a piece of working unit, car, machinery for something else, whatever. This is within a factory, though.
The dynamics, the logistics, of trying to get each unit of material within it's proper place, while being fabricated, have yet to be figured out. It invokes levitation, or, a factory.
It's not going to happen in the basement any time soon, as much as I'd like it.
The government is looking out for it's own interests at all times, just like any organism would. They're not going to "prevent" it, they'll adapt. There will always be government, there will always be churches, there will always be a higher power regardless of how happy each human feels. Humans were built in a structured society. Each person needs a higher power to model themselves after.
apt-get is just so easy to use that I do a minimal Debian install, deselecting even the carefully put-together "desktop", "server", etc options, then install whatever is necessary on the machine as time goes on
Suppose there are 100 tarantula communities scattered around the globe. 99 of them have a weak poison that predators cannot taste. One of them leaves a burning sensation. After a couple of sacrificial tarantula the remaining in the community may live unmolested.
Dell's nVidia Windows drivers supply multiple desktops. I use them both on a workstation and a laptop. Not as solid as X but they get the job done pretty well (aside from lazy mouse window activation across desktops and other sorts of "corner" issues).
They also play terribly with Visual Studio, but VS hasn't played well with others many times.
All I'm saying is that if you know that the computer will be up and waiting for you to resume work at any given time then it is worth starting 20 different "areas" for each project. There is no reason for me to consolidate things into one space because each project is a flick-of-the-fingers away.
I didn't mention that my wife has a complete set of another 20 open windows on the same computer, a keystroke away from my own login. Ctrl-Alt-F8 for her to access her complete 5 desktops with Mozilla, some CD-burning thing, looks like picture management, and who knows what else is open.
The idea is that if you know the computer will be stable then you can start whatever you want, leave it running, and walk away to resume at any time.
To be honest, I can't begin to understand how you would need 25 windows...
I have twenty desktops and an average of two or so windows, including terminals, open on each of them. I also have three different VNC sessions running on other machines, with multiple desktops in each of them. I just checked the uptime on this workstation and it's about two months. The 40 open windows (plus who knows how many others I expect to be there at all times) is actually more a reflection of a stable work environment than anything.
Desktop #1: system things Desktop #2: web browsing Desktop #3: coding Desktop #4: running the program I'm coding Desktop #5: email Desktop #6: VNC (irc and whatnot in there) Desktop #7: VMWare (running Windows for Adobe Illustrator) Desktop #8: alternate coding environment for a different project Desktop #9: alternate program running environment Desktop #10: VNC to a campus computer Desktop #11: syslog output and whatnot for a machine in a different state that I'm responsible for Desktop #12: xmms and interface with my web radio Desktop #13: VNC to a usenet client Desktop #14: I don't use that one for some reason Desktop #15: pr0n, baby Desktop #16: foreign sysadmin things Desktop #17: Matlab Desktops #18-#20: miscellaneous
If you know that the computer is stable, there is no reason to not isolate projects from each other in different places and expect them to still be in the same state when you get back. That's how I end up with tons of windows.
Keep on with your opinion about this fiasco. I totally agree so far.
This kind of blurred distinction between commerce/fun was bound to happen. Gold-farmers, Everquest accounts, selling worthless WoW items on eBay, it's all interesting. As low-handed as this person may come across, the developers, the creators, of this situation took on the responsibility. They were revelling in the idea of selling virtual product for cash... they slipped.
IMO, if you're going to build a fortress and whip up products to sell outside of its doors, to the masses, you can't just go running around to the GODS and expect help when a thief finds a backdoor.
My wife is a Biogeoastrophysiochemistectarianologist. She observes biogeoastrophysiochemistectarian meetings on Sundays. They meet nearby. Her dissertation covers the effects of caffeine on biogeoastrophysiochemistectarian speculations regarding climatological changes and implications on Saturn's moons. Caffeine intake is strongly correlated with wild-ass guesses and hand-waving.
And Frendibulate frendibulates. And Groofundulize groofundulizes
But those are nonsense words. Vi didn't invent "insert" and "append". Those words are commonly used by people that don't know vi.
One person suggested reducing the complexity of vi by making only one insert/append. That would eliminate a style of vi thinking, though. Insert here, append there. Insert blank line and start typing here or after this line. Paste here or after this line, word, etc.
Why throw away this functionality?
CUA behavior of shifted arrow keys: I don't know what that means, sorry. I assume that means highlighting, but that's done through visual mode.
Yanking/deleting into a single register can be done by using the named registers A-Z. Anything put into those registers is appended to what's already there.
Re:My history with VIM
on
Vim 7 Released
·
· Score: 2, Informative
For exactly the reason you mentioned, cursor placement. Insert inserts and append appends. They're fundamentally different approaches and, as such, they have different behaviors. They also extend to such places wherein you can also use "shift-i" to insert at the beginning of the line or "shift-a" to append to the end of a line.
Append becomes very useful if you're writing a quick macro to tack or change something onto/in a filename and you don't want to bother with a shell script.
Suppose, for example, that you have a few files in a directory:
pic1.gif pic2.gif pic3.gif pic4.gif
And you want to convert them all to PNG. You can do this a few ways, but, these are what I use most commonly:
method 1, with bash) for i in `ls *.gif`; do convert $i ${i%gif}png; done
method 2, with vim) bash> ls *.gif > dothis; vim dothis [now, in vim] q1 [macro in register 1] yy [yank this line] p [paste it below] k [move back up a line] J [join the two lines together] A ["append"] bksp-bksp-bksp [erase the gif extension] i ["insert"] png esc 0 [go back to the beginning of the line] j [move down a line] q [quit the macro] 10@1 [do that ten times] 1G [go back to the first line] q1iconvert j0q10@1 [insert a bunch of converts]:wq [save and quit] bash> sh dothis
It looks more complicated than it is. Each step is simple and easy. It's only when you write it all down that it looks hard. The whole point of vi(m) is to stay the hell out of the way and let you move things around as easily as possible.
Slashdot Mirror
I tried clicking on your "see Britney nude" link but it didn't work.
I had three Lifestyle Lifts and now have more confidence than ever. I look good, feel confident, and just landed a new high-paying job. I don't know why the government is giving them a hard time. Don't they have something else to do, like fight crime or win wars or something?
you're the one that said prokaryote ... you're talking about a virus
nein
Matter duplication is a tricky problem. Assembling the integral units is already an issue. 3D printers carve matter out of chalk, cardboard, or wax, not a chunk of metal necessary for transmitting energy from the front to the back of a car.
We have the ability to fabricate a plan into a gear or another hunk of metal. Push the AutoCAD specs into a fab. We, as in humanity, also have used robots to assemble those fabricated hunks into a piece of working unit, car, machinery for something else, whatever. This is within a factory, though.
The dynamics, the logistics, of trying to get each unit of material within it's proper place, while being fabricated, have yet to be figured out. It invokes levitation, or, a factory.
It's not going to happen in the basement any time soon, as much as I'd like it.
The government is looking out for it's own interests at all times, just like any organism would. They're not going to "prevent" it, they'll adapt. There will always be government, there will always be churches, there will always be a higher power regardless of how happy each human feels. Humans were built in a structured society. Each person needs a higher power to model themselves after.
tl;dr fuck you
using bluetooth, the iPhone pauses the song for you to deal with the incoming call on your headset, then resumes when you hang up
Not brilliant, but pretty convenient.
ssh and tunnelling
Fuck everything, we're doing five blades.
Yeah, I had a self-policing points/voting system in mind years ago. Great minds must think alike.
This is AFTER you have him fix the locking mechanism, of course, which makes it tricky.
Bilbo kills Smaug? Well, thanks for ruining it all.
JUST THANKS.
you guys talk a lot
yeah, I do the same thing
apt-get is just so easy to use that I do a minimal Debian install, deselecting even the carefully put-together "desktop", "server", etc options, then install whatever is necessary on the machine as time goes on
I don't know about the rest of you, but I've never felt the urge to lick someone's blog.
Then you, sir, have not been going to the right places: NSFW
[not associated, just a fan]
This reminds me of Oryx and Crake by Margaret Atwood. Good book.
- Donate to the Cowboy Neal Retirement Fund
- Give it to Sony
-
PROFIT!
Suppose there are 100 tarantula communities scattered around the globe. 99 of them have a weak poison that predators cannot taste. One of them leaves a burning sensation. After a couple of sacrificial tarantula the remaining in the community may live unmolested.
Same concept as for the plant.
Dell's nVidia Windows drivers supply multiple desktops. I use them both on a workstation and a laptop. Not as solid as X but they get the job done pretty well (aside from lazy mouse window activation across desktops and other sorts of "corner" issues).
They also play terribly with Visual Studio, but VS hasn't played well with others many times.
All I'm saying is that if you know that the computer will be up and waiting for you to resume work at any given time then it is worth starting 20 different "areas" for each project. There is no reason for me to consolidate things into one space because each project is a flick-of-the-fingers away.
I didn't mention that my wife has a complete set of another 20 open windows on the same computer, a keystroke away from my own login. Ctrl-Alt-F8 for her to access her complete 5 desktops with Mozilla, some CD-burning thing, looks like picture management, and who knows what else is open.
The idea is that if you know the computer will be stable then you can start whatever you want, leave it running, and walk away to resume at any time.
To be honest, I can't begin to understand how you would need 25 windows...
I have twenty desktops and an average of two or so windows, including terminals, open on each of them. I also have three different VNC sessions running on other machines, with multiple desktops in each of them. I just checked the uptime on this workstation and it's about two months. The 40 open windows (plus who knows how many others I expect to be there at all times) is actually more a reflection of a stable work environment than anything.
Desktop #1: system things
Desktop #2: web browsing
Desktop #3: coding
Desktop #4: running the program I'm coding
Desktop #5: email
Desktop #6: VNC (irc and whatnot in there)
Desktop #7: VMWare (running Windows for Adobe Illustrator)
Desktop #8: alternate coding environment for a different project
Desktop #9: alternate program running environment
Desktop #10: VNC to a campus computer
Desktop #11: syslog output and whatnot for a machine in a different state that I'm responsible for
Desktop #12: xmms and interface with my web radio
Desktop #13: VNC to a usenet client
Desktop #14: I don't use that one for some reason
Desktop #15: pr0n, baby
Desktop #16: foreign sysadmin things
Desktop #17: Matlab
Desktops #18-#20: miscellaneous
If you know that the computer is stable, there is no reason to not isolate projects from each other in different places and expect them to still be in the same state when you get back. That's how I end up with tons of windows.
This is one of the best posts I've read in a long time.
Sycraft-fu,
... they slipped.
Keep on with your opinion about this fiasco. I totally agree so far.
This kind of blurred distinction between commerce/fun was bound to happen. Gold-farmers, Everquest accounts, selling worthless WoW items on eBay, it's all interesting. As low-handed as this person may come across, the developers, the creators, of this situation took on the responsibility. They were revelling in the idea of selling virtual product for cash
IMO, if you're going to build a fortress and whip up products to sell outside of its doors, to the masses, you can't just go running around to the GODS and expect help when a thief finds a backdoor.
Biogeoastrophysiochemist
My wife is a Biogeoastrophysiochemistectarianologist. She observes biogeoastrophysiochemistectarian meetings on Sundays. They meet nearby. Her dissertation covers the effects of caffeine on biogeoastrophysiochemistectarian speculations regarding climatological changes and implications on Saturn's moons. Caffeine intake is strongly correlated with wild-ass guesses and hand-waving.
IT'S A FACT!
"Biogeochemistry"? You just made that up.
When I was a grad student in Physioarchaeanthropology we would create tradition Egyptian coffee brews for kicks.
And Frendibulate frendibulates. And Groofundulize groofundulizes
But those are nonsense words. Vi didn't invent "insert" and "append". Those words are commonly used by people that don't know vi.
One person suggested reducing the complexity of vi by making only one insert/append. That would eliminate a style of vi thinking, though. Insert here, append there. Insert blank line and start typing here or after this line. Paste here or after this line, word, etc.
Why throw away this functionality?
CUA behavior of shifted arrow keys: I don't know what that means, sorry. I assume that means highlighting, but that's done through visual mode.
Yanking/deleting into a single register can be done by using the named registers A-Z. Anything put into those registers is appended to what's already there.
For exactly the reason you mentioned, cursor placement. Insert inserts and append appends. They're fundamentally different approaches and, as such, they have different behaviors. They also extend to such places wherein you can also use "shift-i" to insert at the beginning of the line or "shift-a" to append to the end of a line.
:wq [save and quit]
Append becomes very useful if you're writing a quick macro to tack or change something onto/in a filename and you don't want to bother with a shell script.
Suppose, for example, that you have a few files in a directory:
pic1.gif pic2.gif pic3.gif pic4.gif
And you want to convert them all to PNG. You can do this a few ways, but, these are what I use most commonly:
method 1, with bash)
for i in `ls *.gif`; do convert $i ${i%gif}png; done
method 2, with vim)
bash> ls *.gif > dothis; vim dothis
[now, in vim]
q1 [macro in register 1]
yy [yank this line]
p [paste it below]
k [move back up a line]
J [join the two lines together]
A ["append"]
bksp-bksp-bksp [erase the gif extension]
i ["insert"]
png
esc
0 [go back to the beginning of the line]
j [move down a line]
q [quit the macro]
10@1 [do that ten times]
1G [go back to the first line]
q1iconvert j0q10@1 [insert a bunch of converts]
bash> sh dothis
It looks more complicated than it is. Each step is simple and easy. It's only when you write it all down that it looks hard. The whole point of vi(m) is to stay the hell out of the way and let you move things around as easily as possible.