Hey everyone,
I assume that I am missing something which is obvious to everyone, but I can't seem to be able to save a file in TextMate which I have opened with the "Edit in TextMate" command in Transmit 3.02. When I try to save it just beeps and ignores me. It works in eg. SubEthaEdit, and it is exactly what I bought TextMate for, so it annoys me a little.
Is this an error in Transmit, or something I'm missing?
anr
Stupid gravity! -- Homer Simpson
I thought the same and then checked the file I had previously edited and it did have the changes. The beep seems to mean that the change was saved. I definitely think that this behavior is strange as beeps usually mean that something went wrong.
On Mar 6, 2005, at 10:27 AM, Andreas Næsby Rasmussen wrote:
Hey everyone,
I assume that I am missing something which is obvious to everyone, but I can't seem to be able to save a file in TextMate which I have opened with the "Edit in TextMate" command in Transmit 3.02. When I try to save it just beeps and ignores me. It works in eg. SubEthaEdit, and it is exactly what I bought TextMate for, so it annoys me a little.
Is this an error in Transmit, or something I'm missing?
anr
Stupid gravity! -- Homer Simpson
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Op 6-mrt-05 om 16:56 heeft Michael Gregoire het volgende geschreven:
I assume that I am missing something which is obvious to everyone, but I can't seem to be able to save a file in TextMate which I have opened with the "Edit in TextMate" command in Transmit 3.02. When I try to save it just beeps and ignores me. It works in eg. SubEthaEdit, and it is exactly what I bought TextMate for, so it annoys me a little.
Is this an error in Transmit, or something I'm missing?
I thought the same and then checked the file I had previously edited and it did have the changes. The beep seems to mean that the change was saved. I definitely think that this behavior is strange as beeps usually mean that something went wrong.
Yeah, I hate that …
On 6 mars 05, at 17:18, Nednieuws wrote:
Op 6-mrt-05 om 16:56 heeft Michael Gregoire het volgende geschreven:
I assume that I am missing something which is obvious to everyone, but I can't seem to be able to save a file in TextMate which I have opened with the "Edit in TextMate" command in Transmit 3.02. When I try to save it just beeps and ignores me. It works in eg. SubEthaEdit, and it is exactly what I bought TextMate for, so it annoys me a little.
Is this an error in Transmit, or something I'm missing?
I thought the same and then checked the file I had previously edited and it did have the changes. The beep seems to mean that the change was saved. I definitely think that this behavior is strange as beeps usually mean that something went wrong.
Yeah, I hate that …
At first, I missed the Fugu bouncing icon, but after some time I kind of like Transmit behaviour. When you miss the bouncing icon, you're not sure it worked... In Transmit, if you check "beep when transfer completes" in the prefs, you have two beeps: one when you save and one when the file has been uploaded. This is good for the "Have I really saved the file?" paranoia. ;)
But I agree that they should provide different notification methods, at least give us the choice to use different sounds...
-- Fred
On Mar 6, 2005, at 19:34, Fred B. wrote:
In Transmit, if you check "beep when transfer completes" [...] But I agree that they should provide different notification methods, at least give us the choice to use different sounds...
OMG! Are they using the normal error beep for this? I'd say whether or not they should change it is not even up for discussion.
The authors of Transmit should read about Pavlov's dogs: http://en.wikipedia.org/wiki/Conditioning
The most famous example of conditioning involves the development of conditional salivary responses in Pavlov's dogs. If a tone was reliably sounded before the dogs were fed, the dogs would eventually start salivating when they heard the tone, even if no food was present. The dog's responses (salivation) to the tone are said to be conditional upon the dogs' experience with the pairings of the tone and food. Dogs that have not experienced this condition do not salivate when they hear tones. Pavlov's dogs are therefore said to have been conditioned. Their reactions to the tone have been changed through experience.
The same mechanism exists in humans as well, and if the Transmit guys are indeed using the error tone, or something very similar sounding, they are both triggering a false sense of alarm with the user, and undermining the usefulness of the sound as well.
Seems like the smart thing to do would be to support Growl in this case and provide notifications on save and successful upload.
I agree with Allan -- overloading a sound like the error beep is *really* a bad idea, especially when you're reporting success!
Chris
Allan Odgaard wrote:
On Mar 6, 2005, at 19:34, Fred B. wrote:
In Transmit, if you check "beep when transfer completes" [...] But I agree that they should provide different notification methods, at least give us the choice to use different sounds...
OMG! Are they using the normal error beep for this? I'd say whether or not they should change it is not even up for discussion.
The authors of Transmit should read about Pavlov's dogs: http://en.wikipedia.org/wiki/Conditioning
The most famous example of conditioning involves the development of conditional salivary responses in Pavlov's dogs. If a tone was reliably sounded before the dogs were fed, the dogs would eventually start salivating when they heard the tone, even if no food was present. The dog's responses (salivation) to the tone are said to be conditional upon the dogs' experience with the pairings of the tone and food. Dogs that have not experienced this condition do not salivate when they hear tones. Pavlov's dogs are therefore said to have been conditioned. Their reactions to the tone have been changed through experience.
The same mechanism exists in humans as well, and if the Transmit guys are indeed using the error tone, or something very similar sounding, they are both triggering a false sense of alarm with the user, and undermining the usefulness of the sound as well.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 6. mar 2005, at 21:50, Allan Odgaard wrote:
OMG! Are they using the normal error beep for this? I'd say whether or not they should change it is not even up for discussion. [.....] The same mechanism exists in humans as well, and if the Transmit guys are indeed using the error tone, or something very similar sounding, they are both triggering a false sense of alarm with the user, and undermining the usefulness of the sound as well.
Gee... quit with the psycology already ;-), it's just a beep, how hard is it?. We're not dogs after all :-p. Maybe the same mechanism exists in humans, but I am sure we can get used to something working a bit different than normal :-).
On Mar 6, 2005, at 22:13, Sune Foldager wrote:
Gee... quit with the psycology already ;-) [...]
You do know I actually studied psychology, that humans evolved from animals with which we share a lot of our brain and that conditioning is well documented and has been for at least half a century?
We're not dogs [...]
I mentioned Pavlov's dogs because it's a classic experiment and about a hundred years old. A similar classic, that has often been used with humans is:
A human subject or an animal is subjected to an air puff directed to the eye, which elicits a blink reflex. If the air puff is repeatedly preceded by another stimulus, say a tone, the tone will eventually itself elicit a blink just before the air puff.
http://www.mphy.lu.se/avd/nf/hesslow/neuroscience/classcond.html
But it's nice of you to inform us that you are beyond the restraints of basic human physiology and think that software should therefor not take such things into consideration -- I OTOH do!
Get him Allan!
Thank you,
--==<< R i c h a r d B r o n o s k y >>==--
On Mar 6, 2005, at 4:45 PM, Allan Odgaard wrote:
On Mar 6, 2005, at 22:13, Sune Foldager wrote:
Gee... quit with the psycology already ;-) [...]
You do know I actually studied psychology, that humans evolved from animals with which we share a lot of our brain and that conditioning is well documented and has been for at least half a century?
We're not dogs [...]
I mentioned Pavlov's dogs because it's a classic experiment and about a hundred years old. A similar classic, that has often been used with humans is:
A human subject or an animal is subjected to an air puff directed to the eye, which elicits a blink reflex. If the air puff is repeatedly preceded by another stimulus, say a tone, the tone will eventually itself elicit a blink just before the air puff.
http://www.mphy.lu.se/avd/nf/hesslow/neuroscience/classcond.htmlBut it's nice of you to inform us that you are beyond the restraints of basic human physiology and think that software should therefor not take such things into consideration -- I OTOH do!
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 6. mar 2005, at 19:34, Fred B. wrote:
But I agree that they should provide different notification methods, at least give us the choice to use different sounds...
Or use growl for it.
-
Allan Odgaard -
Andreas Næsby Rasmussen -
Bruno Bronosky -
Chris Messina -
Fred B. -
Michael Gregoire -
Nednieuws -
Sune Foldager