On 21.09.2012, at 17:02, Brandon Fryslie <brandon(a)fryslie.com> wrote:
> Dude, we used TM1.
My post was in reply to Randall Hand who has just discovered TextMate and started this discussion on the mailing list. He probably doesn't know the history of TextMate 2. I'm sorry if that wasn't clear.
> Some things are different in TM2, on the vast whole, everything is improved, restructured, cleaned up, and much more powerful.
I haven't really noticed any game changers *for me* in TextMate 2, but that's not supposed to be a complaint.
> Sorry some of the features don't comply with your vague, nebulous specifications.
I don't think there is anything »nebulous« or »vague« about missing TM1-style projects or wanting to have a functional bundle editor. While the latter is a matter of time, the former is a design decision made prior to open sourcing TextMate 2.
> Textmate 2 is open source now, I can't really see how you can complain like you are whatsoever.
There is no reason for ad hominem attacks and acerbic attitude. Where else other than this mailing list should we exchange opinions on how to make TextMate 2 better? After all, the reason we are here is because we like TextMate and we care that eventually we will have 2.0 final on our SSDs (hopefully before I get tenure, though ;-)).
Max
On 21.09.2012, at 06:44, Travis Dunn <tdunn13(a)gmail.com> wrote:
> I don't think there's anything personal intended here by anyone, but I also think calling someone's work a "huge disappointment" is rather harsh, and will be taken personal if intended that way or not. Also, generally i just disagree with the approach of "I dont want to switch to another editor but if X isn't implemented/fixed, i'll have to", if you need to switch to something that works better for you, go for it. A single editor is never going to be everything to everyone.
I think the disappointment is hard to understand for people who haven't used TM1's projects. You could manage files with TM1 in two ways: either you could either create a project or you could open them as a directory (e. g. by typing »mate .« in the Terminal), and to some people, that was *the* feature that got them sold on TM1. So you can expect that a removal of one of the most important features is going to create an equally large reaction. I was using both modes, most of my stuff was organized in projects, some other things were done in the file browser, and it was *the* feature that got me hooked on TextMate.
The problem with TextMate 1 (for me, at least) is that it has become »creaky« because it hasn't been updated for a very long time in a substantial way (can't quite pin point the time, but feels like 10.4~10.5 time frame, please correct me if I'm wrong). On 10.4, Textmate was the posterboy of a rock solid app, but in 10.6 or so, you could tell that not all of its gears meshed well with OS X new shiny internals (I remember problems with the built-in dictionary, for instance).
What is interesting, though, is that even after all of these years, nobody has really made a better TextMate 1. I've tried the usual suspects, Chocolat, Sublime Text 2, BBEdit, you name them, but they're usually not any better than what we have with TextMate 2 (Chocolat is still 1.0ish and does not have good support for LaTeX, for instance, and Sublime Text 2 does not really feel like a Mac app). TextMate's LaTeX bundle is still the gold standard for me, and it has some features I crucially rely upon (e. g. auto completion of labels and citations), so I won't switch unless another text editor has the same features.
The lead developer and owner of macromates, Allen Oodgard, has made it clear that it was a conscious decision of him to abandon projects in favor of a file-based management (+ .tm_properties). I don't know whether the periodic waves of discussions on the topic will or won't change his mind, but even if they do, there are probably other things on his list of priorities (e. g. a bundle editor in TextMate 2).
However, Project+ was an add-on developed by a third-party, so if TextMate 2 allows for similarly deep »customization«, perhaps this void will be filled by a third party. And now that TextMate 2 is open source, perhaps it can be contributed to the main source? One can dream ;-)
Max
Hello,
I'm having trouble syncing LaTeX in the direction TextMate --> Skim. Specifically, I'm (still) using this script: http://ebundles.googlecode.com/svn/trunk/Bundles/Latex.tmbundle/Commands/Fi…
and the following lines don't work for me:
if [[ "$V" == Skim ]]; then
SCRIPT="$(find_app Skim.app)/Contents/Resources/displayline"
if [[ -x "$SCRIPT" ]]; then
"$SCRIPT" &>/dev/console "$TM_LINE_NUMBER" "$PDF" "$TM_FILEPATH"
else
echo "Unable to locate $V."
fi
fi
I found a workaround which is to comment out and replace as follows
if [[ "$V" == Skim ]]; then
SCRIPT="$(find_app Skim.app)/Contents/Resources/displayline"
# if [[ -x "$SCRIPT" ]]; then
/Volumes/Home/Applications/Skim.app/Contents/SharedSupport/displayline &>/dev/console "$TM_LINE_NUMBER" "$PDF" "$TM_FILEPATH"
# else
# echo "Unable to locate $V."
# fi
fi
That said, I don't understand why I can't get it working in its original form, because find_app appears to work and displayline appears executable:
FZs-MacBook:bin fz$ pwd
/Volumes/Home/Applications/TextMate.app/Contents/SharedSupport/Support/bin
FZs-MacBook:bin fz$ ./find_app Skim.app
/Volumes/Home/Applications/Skim.appFZs-MacBook:bin fz$ ls -l /Volumes/Home/Applications/Skim.app/Contents/SharedSupport/displayline
-rwxr-xr-x@ 1 fz staff 1735 Mar 12 2012 /Volumes/Home/Applications/Skim.app/Contents/SharedSupport/displayline
FZs-MacBook:bin fz$
Can anyone suggest a better fix than my workaround?
Thanks in advance,
Francois
In the latest alpha, my dead keys (set up with Ukelele:
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ukelele)
produce a snippet completion dialogue and have therefore been rendered
unusable.
This is problematic because it means not only can the dead keys not be
used for their alternate purpose, but they can't even be used to insert
the unaltered character.
Best,
Garrett
Hi,
I am updating my website from XHTML to HTML5 along with changing some other
code elements - so there is probably 20-25 different types of code changes
needed in total. Is there a way of building 'all' the required changes into
TextMate and running it so that it changes the code it finds on a given web
page?
I have looked at the 'Find And Replace' tool and it would still be a very
manual process to go through the 200+ web pages individually. Is there a
faster way? Some kind of function?
Thanks
--
View this message in context: http://textmate.1073791.n5.nabble.com/Multiple-Find-And-Replace-Functions-t…
Sent from the textmate users mailing list archive at Nabble.com.
I've installed rmate on a remote server although I'm able to create a new
file on this server, when doing some modification on an existing file, they
aren't saved after the saving and closing on the TextMate side.
The server is running Xubuntu 12.04, ruby 1.9.3 has been installed using
rvm.
the remote file perms are :
-rwxrw-r-- 1 yt yt 455 sept. 6 16:59 menu.zsh
what i did :
$ ssh dell-par
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-30-generic x86_64)
* Documentation: https://help.ubuntu.com/
Last login: Fri Sep 7 09:18:50 2012 from
2a01:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:2559
Linux D620 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
14:49:17 up 5:38, 2 users, load average: 0.11, 0.29, 0.56
yt@D620 /home/yt $ rmate bin/menu.zsh
yt@D620 /home/yt $ cat bin/menu.zsh
#!/usr/bin/zsh
MENU_DIR=${HOME}/bin/scripts
MENU_ITEMS=(`ls ${MENU_DIR}`)
while (( 1 > 0 )) {
i=0
while (( i++ < ${#MENU_ITEMS} )) {
echo "${i} -> ${MENU_ITEMS[i]:r}"
}
echo "${i}|q -> quit"
echo -n "Entrez un nombre de 1 à ${i} (ou q pour quitter). : "
read NUM
if [[ ${NUM} -eq ${i} || ${NUM} == "q" ]]; then
echo "bye!"
exit 0
else
echo "Vous avez choisi '${MENU_ITEMS[${NUM}]:r}'."
${MENU_DIR}/${MENU_ITEMS[${NUM}]}
fi
}
exit $?
yt@D620 /home/yt $
my local ~/.ssh/config file :
$ cat ~/.ssh/config
Host dell-par
User yt
Hostname 2a01:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:a960
RemoteForward 52698 127.0.0.1:52698
Host dell-pal
User yt
Hostname 2a01:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:a960
RemoteForward 52698 127.0.0.1:52698
Host gericom
User yt
Hostname 2a01:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:a07b
RemoteForward 52698 127.0.0.1:52698
also i wonder if it is usefull to put "RemoteForward 52698 127.0.0.1:52698"
for each host.
best
--
Yvon
> -----Original Message-----
> From: textmate-bounces+s.j.holden=brighton.ac.uk(a)lists.macromates.com
> [mailto:textmate-
> bounces+s.j.holden=brighton.ac.uk(a)lists.macromates.com] On Behalf Of
> Allan Odgaard
> Sent: 18 September 2012 10:57
> To: TextMate users
> Subject: [TxMt] Re: Problem saving to NFS share from b9147
>
> On Sep 18, 2012, at 11:39 AM, Steve Holden <S.J.Holden(a)brighton.ac.uk>
> wrote:
>
> > [...] have found a critical bug for me in b9147 [...] set_attributes() failed:
> > Attribute not found.
>
> Afraid the bug is in NFS. If TextMate gets an error from any of the API
> involved during save, it will report that as an error (as it should) and treat the
> file as not saved.
> ...
> There is a 2.0 way to do the same [work-around]:
>
> defaults write com.macromates.TextMate.preview volumeSettings '{
> "/net/" = { extendedAttributes = 0; }; }'.
>
> This will disable them for all paths under /net/ - this setting should be
> moved to .tm_properties, but right now, the above should be a workaround.
Perfect! Thanks for the incredibly quick and helpful response, Alan - TM2 it is then :-)
Are you still considering whether to add a Donate button to the site?
Best wishes,
Steve
___________________________________________________________
This email has been scanned by MessageLabs' Email Security
System on behalf of the University of Brighton.
For more information see http://www.brighton.ac.uk/is/spam/
___________________________________________________________
In the 9309 release of TM2 the placement of the html output window is broken. The placement on the right does not work anymore.
The command
defaults write com.macromates.TextMate.preview htmlOutputPlacement right
does not work. I'm only able to change to a separate windows, i.e.,
defaults write com.macromates.TextMate.preview htmlOutputPlacement window
All the best
Guido
Hi, folks
I’m loving TM v2 – and would love to switch to it full-time, but have found a critical bug for me in b9147 which is making that awkward.
One of my projects is hosted on an old NFS v3 share (hosted on old Solaris 9 server) which is auto-mounted on my Mac Pro (running 10.6.8 – which I’m conscious is becoming deprecated with TM2; I’ll be upgrading to 10.8 soon). The file is owned by a different user, but the share is root-mountable from my workstation, so ‘sudo’ will allow me to update the file.
After making a change to a file, I press CMD-S, enter my credentials, and it prompts with:
The document “filename.pm” could not be saved.
set_attributes() failed: Attribute not found.
The file *is* updated on disk, but the red “close window” icon in the top-left of the window remains in its unsaved state, and TM thinks the file hasn’t been saved.
I’ve tried the TM1-style fix (though I’m not sure whether this still applies to TM2) before restarting TM2:
http://manual.macromates.com/en/saving_files#extended_attributes_metadata
but this doesn’t help.
Logged messages:
$ g textmate /var/log/system.log
Sep 18 10:07:06 [0x0-0x76a76a].com.macromates.TextMate.preview[34899]: TextMate: error unobserving fd 31: No such file or directory
Sep 18 10:07:06 [0x0-0x76a76a].com.macromates.TextMate.preview[34899]: TextMate: error unobserving fd 13: No such file or directory
Sep 18 10:07:07 SecurityAgent[46060]: com.macromates.textmate.openfile|2012-09-18 10:07:07 +0100
Sep 18 10:07:09 [0x0-0x76a76a].com.macromates.TextMate.preview[34899]: authorization (pid 34899): got âcom.macromates.textmate.openfileâ
Sep 18 10:07:09 com.macromates.auth_server[51179]: authorization (pid 51179): got âcom.macromates.textmate.openfileâ
I’m not expecting you to be able to replicate the problem (my condolences if you’re using NFS for anything ;-), but I thought I should report the problem in case it was helpful. Is there anything I could try which would help you troubleshoot this?
If there’s a local change I can make (a .tm_properties file option for the root of the shared folder, say), I’d be grateful for any advice…
(in the meantime, this is all the incentive I need to transition off our old NFS server to our git repo ;-) ).
Best wishes,
Steve
PS my NFS shares are mounted with these options (which usually help with Solaris NFS servers)
$ m /etc/nfs.conf
# Mount options to help ease problems with flaky NFS connections to Solaris 10 NFS (v4) shares
nfs.client.mount.options = vers=3,tcp,resvport,soft,intr,bg,locallocks,rdirplus,nosuid,nodev
___________________________________________________________
This email has been scanned by MessageLabs' Email Security
System on behalf of the University of Brighton.
For more information see http://www.brighton.ac.uk/is/spam/
___________________________________________________________
wondering if anyone can spot what is wrong with this textmate command for
corona sdk? It worked fine until I updated to the latest daily build of
Corona. I tried to change the path variable, but to no avail. Basically
nothing happens when I hit Command-R (whereas normally it would kick off
corona with my project file)
Hi Darren,
Just wondering if you're aware of any changes required to get the RUN
command to work on the latest build of corona? I've tried changing the path
but it still doesn't respond. I'm not quite sure how to get some logging
happening within a textmate bundle...
thanks
Greg
--------------
#!/bin/bash
if [[ ${#SKIN} < 1 ]] ; then
SKIN="iPhone"
fi
CORONA_SIM_PATH="/Applications/CoronaSDK/Corona\ Terminal"
#if [[ ${#SDK_PATH} > 0 ]] ; then
# CORONA_SIM_PATH=$SDK_PATH"/simulator"
#else
# CORONA_SIM_PATH="/Applications/CoronaSDK/Corona\ Terminal"
## CORONA_SIM_PATH="/Applications/CoronaSDK/simulator"
## CORONA_SIM_PATH="/Applications/CoronaSDK/Corona\ Simulator"
#fi
if [[ ${#TM_PROJECT_DIRECTORY} > 0 ]] ; then
TARGET_DIR=$TM_PROJECT_DIRECTORY
else
TARGET_DIR=$TM_DIRECTORY
fi
# In order for the simulator relaunch to work, "Enable access for assistive
devices" must be selected in System Preferences > Universal Access.
osascript <<- APPLESCRIPT
display dialog "I love the MacTipper Blog!"
on appIsRunning(appName)
tell application "System Events" to (name of processes) contains appName
end appIsRunning
on selectAppMenuItem(app_name, menu_name, menu_item)
try
-- bring the target application to the front
tell application app_name
activate
end tell
tell application "System Events"
tell process app_name
tell menu bar 1
tell menu bar item menu_name
tell menu menu_name
click menu item menu_item
end tell
end tell
end tell
end tell
end tell
return true
on error error_message
return false
end try
end selectAppMenuItem
if appIsRunning("Corona Simulator") then
selectAppMenuItem("Corona Simulator","File","Relaunch")
else
tell application "Terminal"
-- tell application "iTerm"
do script "$CORONA_SIM_PATH -project $TM_PROJECT_DIRECTORY -skin $SKIN"
end tell
end if
APPLESCRIPT
--------------
--
View this message in context: http://textmate.1073791.n5.nabble.com/what-is-wrong-with-this-command-code-…
Sent from the textmate users mailing list archive at Nabble.com.
