15 Sep
2005
15 Sep
'05
9:50 a.m.
A few days ago the create new file button in the drawer stopped
working. Whenever I tried to create a new file, TM crashed. Then
whenever I'd go into a terminal to fiddle, I'd get some error (sorry
to so vague) about resource fork not being available.
I would force crash textmate, and killall bash, and all would work
again - but each time I tried to create a file (I sure hope it works
this time...), I had to do it all over again.
Last night I made the same error, textmate crashed, but I never got
to killing the runaway bash process. I woke up and my computer fan
was just screaming, a quick top showed a runaway bash process going
at 75% cpu and fifty others! Here's a snip:
--------------------------------
kjell 26675 74.2 0.1 27880 900 ?? R 1:09AM
430:19.31 /bin/bash -c touch "$TM_NEW_FILE"
kjell 26571 0.4 0.1 27880 980 p3 S 12:57AM 0:00.12
-bash
kjell 26606 0.0 0.1 27880 764 ?? S 1:09AM
0:00.04 /bin/bash -c touch "$TM_NEW_FILE"
kjell 26608 0.0 0.1 27880 508 ?? S 1:09AM
0:00.01 /bin/bash -c touch "$TM_NEW_FILE"
[35 more like the last two...]
--------------------------------
What could be going wrong? I'd love to have it fixed, if possible.
The problem has reared it's ugly head with both beta1.17 and r421,
and is getting to be a real pain. Anyone have an idea what's wrong?
Kjell [http://station11.net]
15 Sep
15 Sep
10:01 a.m.
New subject: check unmatched parenthesis
Hola,
is it possible to add to the menubar a command to check if there are
unmatched parenthesis, brackets, brases and so on for all languages?
I saw in Wiki the request to add a functionality like emacs
parenthesis hilighting: it is a useful think, 'cause not always we
write a new page, and then autocompletion is very nice, but sometimes
we correct an old page, and often there are unmatched parenthesis to
check.
Many thanks
Salvo
5 Oct
5 Oct
10:40 a.m.
New subject: check unmatched parenthesis
On 15/09/2005, at 16.01, salvo wrote:
is it possible to add to the menubar a command to
check if there
are unmatched parenthesis, brackets, brases and so on for all
languages?
If you want something that verifies that the current file is valid,
I'd suggest creating a command that does so. There's already a
validate command (ctrl-shift V) for several languages and formats
that runs the buffer through a syntax checker.
15 Sep
15 Sep
11:52 a.m.
On 15/09/2005, at 15.50, Kjell Olsen wrote:
A few days ago the create new file button in the
drawer stopped
working. Whenever I tried to create a new file, TM crashed. Then
whenever I'd go into a terminal to fiddle, I'd get some error
(sorry to so vague) about resource fork not being available.
When you create a new empty file, TM uses the Empty file template,
which just does a “touch” on the filename, and based on your process
dump, this is what fails.
Sounds like you have a (serious) problem with your filesystem.
Is this normal HFS+ / Tiger? and can you create files by other means?
14 Nov
14 Nov
12:38 p.m.
New subject: TextMate crashes and runaway bash processes (still)
I've been having an issue (see below) with running any command from
textmate: whenever I try, textmate seizes up and starts spawning
unsuccessful processes.
Earlier Allen said it might be a disk format error, and indeed, my
disk was past the point of being repairable by Disk Utility. I wiped
and reformatted - only to still have the same error, but neither disk
utility nor fsck finds anything wrong with the disk.
While TM is spinning its gears (and spawning numerous bash
processes), anything I try to do in terminal gives me "-bash: fork:
Resource temporarily unavailable". Force TM to Quit and I get fork
back, so I can kill the bash processes and bring my CPU load back
down from 100%. I haven't seen anything show up in the console.
I keep up with the most current builds, am running on 10.4.3 (but the
problem occurred earlier with 10.4.2) on a 1.5ghz powerbook with
768MB RAM.
Any ideas?
-kjell
On Sep 15, 2005, at 8:50 AM, Kjell Olsen wrote:
A few days ago the create new file button in the
drawer stopped
working. Whenever I tried to create a new file, TM crashed. Then
whenever I'd go into a terminal to fiddle, I'd get some error
(sorry to so vague) about resource fork not being available.
I would force crash textmate, and killall bash, and all would work
again - but each time I tried to create a file (I sure hope it
works this time...), I had to do it all over again.
Last night I made the same error, textmate crashed, but I never got
to killing the runaway bash process. I woke up and my computer fan
was just screaming, a quick top showed a runaway bash process going
at 75% cpu and fifty others! Here's a snip:
--------------------------------
kjell 26675 74.2 0.1 27880 900 ?? R 1:09AM
430:19.31 /bin/bash -c touch "$TM_NEW_FILE"
kjell 26571 0.4 0.1 27880 980 p3 S 12:57AM
0:00.12 -bash
kjell 26606 0.0 0.1 27880 764 ?? S 1:09AM
0:00.04 /bin/bash -c touch "$TM_NEW_FILE"
kjell 26608 0.0 0.1 27880 508 ?? S 1:09AM
0:00.01 /bin/bash -c touch "$TM_NEW_FILE"
[35 more like the last two...]
--------------------------------
What could be going wrong? I'd love to have it fixed, if possible.
The problem has reared it's ugly head with both beta1.17 and r421,
and is getting to be a real pain. Anyone have an idea what's wrong?
Kjell [http://station11.net]
12:49 p.m.
New subject: TextMate crashes and runaway bash processes (still)
On 14/11/2005, at 18.38, Kjell Olsen wrote:
I've been having an issue (see below) with running
any command from
textmate: whenever I try, textmate seizes up and starts spawning
unsuccessful processes.
Someone else had a similar problem: When running commands, TextMate
will source your /etc/profile, and then your ~/.bash_profile (if
there's none: ~/.bash_login, and if that's missing: ~/.profile).
This is to setup proper path. The problem that the other person had
was, that one of these files started a new bash shell, and since
BASH_ENV is setup for TM, that new bash will go through the same
procedure, so recursively starting new bash instances…
You can disable this by doing:
touch "$HOME/Library/Application Support/TextMate/bash_init.sh"
Basically that'll just source that file instead of your normal /etc/
profile -- this is not the recommended, since you then won't get a
normal bash PATH (but you could set that up in the bash_init.sh).
The proper workaround would be to check the /etc/profile and
~/.bash_profile -- you're welcome to post these.
12:51 p.m.
New subject: TextMate crashes and runaway bash processes (still)
On 14/11/2005, at 18.49, Allan Odgaard wrote:
[...] The problem that the other person had was, that
one of these
files started a new bash shell, and since BASH_ENV is setup for TM
[...]
And btw, I'll unset BASH_ENV when starting commands starting with
next build, so that'd also be a fix for this :)
5423
days inactive
5484
days old
7 comments
4 participants
participants (4)
-
Allan Odgaard -
Allan Odgaard -
Kjell Olsen -
salvo