I hate seeing the ~ turds when I list, but liked having them in their directory when I need them. Thus prefixing save files with a dot to merely hide them.
Breaks dired-mode, but I don't really use it. If anyone knows why offhand, please share the knowledge.
;; hidden backup files - i hate seeing them in listings... ;; prefix with a dot as well as postfix with a tilde
(defun custom-make-backup-file-name ( file )
(let ((d (file-name-directory file))
(f (file-name-nondirectory file)))
(concat d "." f "~")))
(setq make-backup-file-name-function 'custom-make-backup-file-name)
It is true that common shorthand characters given silly names are rarely interchangeable with genuine musical notation, although sometimes said musical notation is most easily represented by just using a similar shorthand character that is already found on the keyboard.
If you had to write an example of a flat sign given only a keyboard, a lower-cased b would probably suit your purpose just fine.
So, assuming I repost her diaries, I should think again before casually time traveling to before 1582 and ignorantly expecting the days to line up appropriately?
Your argument is dumb. They're not taking your things when they "steal wifi". They are sending you messages you've happily configured your equipment to forward along. It's more like I handed you snail-mail, each envelope containing another envelope and a request to forward it off. If you waste time sending along my letters, I'm not doing anything criminal. This is how public wifi operates.
Either properly configure your radio signal or keep it the hell off of my lawn.
I agree. In all these discussions on what editor to use, we never get to hear about the embedded systems angle. Have you ever tried to bring up emacs on a wafer thin mp3 player? I think not. When it comes to embedded, vi is the only way to fly.
I'm curious, how often do you bring up vi on your mp3 player?
--
M-x work-on-a-wafer-thin-mp3-player-mode
Once you accepted the fact that it was blue, there wasn't a whole lot different, apart from the start menu (and both of those things could easily be disabled, and frequently were)
Perception is reality. At least, that's been my perception.
Of course, being "home users", a local privilege escalation just means the one person using the box will have a brand new way to `sudo' until the new kernel patches roll around. This thing is not a danger unless a) you've already been hit with a remote sploit giving someone access to the box, or b) this is a shared system, which most home systems likely aren't. So unless you're hacked by other means, most home users won't have a problem with this. Businesses on the other hand...
"At the dawn of the millennium, the nation collapsed. At fifteen percent unemployment, ten million were out of work. 800,000 students boycotted the school. The adults lost confidence, and fearing the youth, eventually passed the Millennium Educational Reform Act AKA: The BR Act..."
Wow. I imagined their system as just being a statistical analyzer hooked up to a computer program map they would use to send out emails with information for officers coming onto duty to read/be briefed with before going out.
Actually having some two bit cliché weatherman delivering a stand up crime forecast on the evening news? Awesome. Let's go ahead and lampoon him in front of a large projection of a time loop with a cloud of looters moving east to west over the city and little pinup mugger glyphs with percentages popping up in different spots.
/ And blue hair. You gotta have blue hair.// Hoping it's still 'a little like this'/// Long live strongbadia.
A web app only appears to be no different because of clever programs you already have. You send it a document that asks for a document, and the server sends you a document back. You are not running anything more on the remote server by sending it bits than they are running software on your machine by sending you bits back.
If merely interacting with a remote system is to be considered a form of distribution than every GPLv3 email server will have to give up its source to anyone that happens to email it. Every irc server will have to give it to anyone chatting on it. Every router to anyone that shoots a ping or two past it. Since its all based on sockets and internet protocol, and I am remotely using your protocol handlers to communicate, I guess you owe me those as well. If your web server uses a secondary sql server does the source owe bleed over to that, too? Hell, why not? It is all still to process my document, after all. So don't forget I get everything on there too.
The current reasonable compulsory giving of source upon choosing to become a distributor becomes unreasonable compulsory giving of source to every nitwit that happens to send you an email, or visit your homepage. For everybody. It is ludicrous to even suggest.
Where is the line drawn?
If they send a request document to a site I have made they are "remotely using" any of custom web pages, document generators, Apache, PHP, Python, Perl, MySQL, all of their libraries, the Linux kernel itself. Those probably forked off of bash and sysvinit. Does that count?
If I had GPLv3 components doing any of these jobs, am I now forced to bother with sourcing them over to everyone that happens to follow a link to a site? It is silly.
If you want to get legalistic, I could argue that putting the web app on the website isn't usage so much as performance.
Cool.
http://www.bitlaw.com/copyright/scope.html#perfo rmance Public Performance:
The public performance right allows the copyright holder to control the public performance of certain copyrighted works. The scope of the performance right is limited to the following types of works:
But the rest of your comments are spurious. For instance: Software patents: totally ridiculous, and putting a huge hurt on an area that should be boiling with creativity.
Are you seriously suggesting that software isn't boiling with creativity? Look at everything Google is doing, and all of the Linux distros, and all of the stuff on SourceForge. Look at the rapid development of Web 2.0 apps in the last two years. Look at the rate of deployment of software across a huge range of devices, from 64-bit super-pipelined machines to UMPCs to dinky cellphone processors. What part of this is "crippled?" Software development is limited only by the rate of our collective imagination. Patents aren't hampering anything.
What are you defending here? His position is that patents hurt innovation and part of your defense is that a lot of non-patented free software is being written? You realize that open source _is_ harmed by patents don't you? Even if it wasn't, patents surely don't help it. Patents are the only thing that can hurt free software. They are an anathema to it. All of the software you mentioned exists by the spurious whim of those given patent rights over the general concepts it utilizes to implement its functionality.
The US patent system is a well of misery, corporate bootlicking, and "let's crush the little guy" methodologies.
Again, you are misinformed. Patents are too expensive to assert against "little guys." Patents are almost solely used by large corporations against other large corporations. In practice, the "little guys" - sole inventors - are almost never accused with patent infringement. Why bother? It's too expensive, and there's no benefit for the corporation.
And no chance for the little guy to defend his patent rights from casual theft, as he lacks the monetary resource to defend himself. His only recourse is to find a lawyer who will operate on the promise of a future win and to wait years and possibly decades for their suit to go through.
Gentlemen, we must find a way to plug the analog instrument hole. Only pre-approved instruments with prerecorded and approved music will be sold. With our new patented `like-playing' technology, customers can feel like they're actually playing. Any fair-licensed author-play instruments detecting the play of copyrighted works will immediately call home to beat those pirates and keep sales cost low!
With my community gone, to continue as before was impossible. Instead,
I faced a stark moral choice.
The easy choice was to join the proprietary software world, signing
nondisclosure agreements and promising not to help my fellow hacker.
Most likely I would also be developing software that was released
under nondisclosure agreements, thus adding to the pressure on other
people to betray their fellows too.
I could have made money this way, and perhaps amused myself writing
code. But I knew that at the end of my career, I would look back on
years of building walls to divide people, and feel I had spent my life
making the world a worse place.
I had already experienced being on the receiving end of a
nondisclosure agreement, when someone refused to give me and the MIT
AI lab the source code for the control program for our printer. (The
lack of certain features in this program made use of the printer
extremely frustrating.) So I could not tell myself that nondisclosure
agreements were innocent. I was very angry when he refused to share
with us; I could not turn around and do the same thing to everyone
else.
Another choice, straightforward but unpleasant, was to leave the
computer field. That way my skills would not be misused, but they
would still be wasted. I would not be culpable for dividing and
restricting computer users, but it would happen nonetheless.
So I looked for a way that a programmer could do something for the
good. I asked myself, was there a program or programs that I could
write, so as to make a community possible once again?
The answer was clear: what was needed first was an operating system.
That is the crucial software for starting to use a computer. With an
operating system, you can do many things; without one, you cannot run
the computer at all. With a free operating system, we could again have
a community of cooperating hackers--and invite anyone to join. And
anyone would be able to use a computer without starting out by
conspiring to deprive his or her friends.
As an operating system developer, I had the right skills for this job.
So even though I could not take success for granted, I realized that I
was elected to do the job. I chose to make the system compatible with
Unix so that it would be portable, and so that Unix users could easily
switch to it. The name GNU was chosen following a hacker tradition, as
a recursive acronym for "GNU's Not Unix."
from/usr/share/emacs/21.4/etc/THE-GNU-PROJECT
by Richard Stallman
The choice of liberty in all things, even things so small as a printer driver.
Slashdot Mirror
I just glanced on wikipedia. Apparently Bill Joy wrote vi the same year that Stallman et al wrote the macros for TECO. ( '76 for each )
;; hidden backup files - i hate seeing them in listings...
;; prefix with a dot as well as postfix with a tilde
(defun custom-make-backup-file-name ( file )
(let ((d (file-name-directory file))
(f (file-name-nondirectory file)))
(concat d "." f "~")))
(setq make-backup-file-name-function 'custom-make-backup-file-name)
(defun backup-file-name-p ( file )
(let ((letters (string-to-list (file-name-nondirectory file))))
(and (> 2 (length letters))
(equal "." (first letters))
(equal "~" (last letters)))))
(defun file-name-sans-versions ( file )
(if (not (backup-file-name-p file))
file
(let ((d (file-name-directory file))
(f (file-name-nondirectory file)))
(let ((letters (string-to-list f)))
(concat d (subseq letters 1 (- (length f) 1)))))))
Proper indentation is left as an exercise for the slashdot administrators.
I can do some pretty evil stuff in .BAT files...
It is true that common shorthand characters given silly names are rarely interchangeable with genuine musical notation, although sometimes said musical notation is most easily represented by just using a similar shorthand character that is already found on the keyboard. If you had to write an example of a flat sign given only a keyboard, a lower-cased b would probably suit your purpose just fine.
Category : People that annoy you ...
// you'll get over it
| | N | _ | G | G | E | R | S | |
I wouldn't say the reaction would be very big if done well.
/ south park
So, assuming I repost her diaries, I should think again before casually time traveling to before 1582 and ignorantly expecting the days to line up appropriately?
This baby is a fully loaded supercomputing* monster!
* term may only apply to regions trapped between the years 1950 to 1980.
I use the left-windows key as the open new terminal key. Very convenient.
Your argument is dumb. They're not taking your things when they "steal wifi". They are sending you messages you've happily configured your equipment to forward along. It's more like I handed you snail-mail, each envelope containing another envelope and a request to forward it off. If you waste time sending along my letters, I'm not doing anything criminal. This is how public wifi operates.
Either properly configure your radio signal or keep it the hell off of my lawn.
I agree. In all these discussions on what editor to use, we never get to hear about the embedded systems angle. Have you ever tried to bring up emacs on a wafer thin mp3 player? I think not. When it comes to embedded, vi is the only way to fly.
I'm curious, how often do you bring up vi on your mp3 player?
--
M-x work-on-a-wafer-thin-mp3-player-mode
Of course, being "home users", a local privilege escalation just means the one person using the box will have a brand new way to `sudo' until the new kernel patches roll around. This thing is not a danger unless a) you've already been hit with a remote sploit giving someone access to the box, or b) this is a shared system, which most home systems likely aren't. So unless you're hacked by other means, most home users won't have a problem with this. Businesses on the other hand...
Or wasted. We aren't exactly closed systems you know.
Don't be silly. It isn't losing, Microsoft is dead, remember?
Wow. I imagined their system as just being a statistical analyzer hooked up to a computer program map they would use to send out emails with information for officers coming onto duty to read/be briefed with before going out.
// Hoping it's still 'a little like this' /// Long live strongbadia.
Actually having some two bit cliché weatherman delivering a stand up crime forecast on the evening news? Awesome. Let's go ahead and lampoon him in front of a large projection of a time loop with a cloud of looters moving east to west over the city and little pinup mugger glyphs with percentages popping up in different spots.
/ And blue hair. You gotta have blue hair.
It's a bit muggery out there today folks, with a thirteen percent chance of homicide over on 5th. So remember to don those kevlars. Back to you, Tom.
If merely interacting with a remote system is to be considered a form of distribution than every GPLv3 email server will have to give up its source to anyone that happens to email it. Every irc server will have to give it to anyone chatting on it. Every router to anyone that shoots a ping or two past it. Since its all based on sockets and internet protocol, and I am remotely using your protocol handlers to communicate, I guess you owe me those as well. If your web server uses a secondary sql server does the source owe bleed over to that, too? Hell, why not? It is all still to process my document, after all. So don't forget I get everything on there too.
The current reasonable compulsory giving of source upon choosing to become a distributor becomes unreasonable compulsory giving of source to every nitwit that happens to send you an email, or visit your homepage. For everybody. It is ludicrous to even suggest.
Where is the line drawn?
If they send a request document to a site I have made they are "remotely using" any of custom web pages, document generators, Apache, PHP, Python, Perl, MySQL, all of their libraries, the Linux kernel itself. Those probably forked off of bash and sysvinit. Does that count?
If I had GPLv3 components doing any of these jobs, am I now forced to bother with sourcing them over to everyone that happens to follow a link to a site? It is silly.
Cool.
I don't see "remote document processing" under the approved list of performance based copy rights.
and even the rate of change itself depends upon the rate at which the changing entity moves through space
Actually it's the "when will this be compatible with the people" part that is unsettling. / probably not // Imperius Curse ?
Gentlemen, we must find a way to plug the analog instrument hole. Only pre-approved instruments with prerecorded and approved music will be sold. With our new patented `like-playing' technology, customers can feel like they're actually playing. Any fair-licensed author-play instruments detecting the play of copyrighted works will immediately call home to beat those pirates and keep sales cost low!
from
by Richard Stallman
The choice of liberty in all things, even things so small as a printer driver.