Just ran into this problem today. In our project, we have several
files that our mirrored, so we use git to manage the symlinks. Today
we discovered that you can open a symlinked file, but when you try to
go and save it, the symlink is erased and replaced with a brand new
file, rather than updating the contents of the file that the symlink
points to.
Is this a known issue? Is there any suggested workaround for it?
(other than, make sure you don't edit a symlinked file?)
Thanks,
Tim
I've found a bug in the Ruby bundle for Textmate. Under certain
circumstances, using Control-Q to reformat comment code raises an exception
that spews error code into the source.
Is this the right forum to post bugs in Ruby bundles?
The problem occurs if you have a comment that contains a single word that
goes past column 79. For example, in the following code (also attached) the
x's in the comment extend out to column 80:
#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
def func(x,y)
x+y
end
If you place the caret inside the comment and press control-Q you see the
following:
/Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:365:in
/bin/bash: +': invalid option
Usage: /bin/bash [GNU long option] [option] ...
/bin/bash [GNU long option] [option] script-file ...
GNU long options:
--debug
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--rcfile
--restricted
--verbose
--version
--wordexp
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o optionwrite'
from
/Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:408
def func(x,y)
x+y
end
This doesn't happen if the word in the comment stops before column 80.
This isn't an impossible scenario because it's easy to have a URL in your
documentation that's more than 80 characters long.
--
Bill McNeill
http://staff.washington.edu/billmcn/index.shtml
I am a recent TextMate convert. Part of what swayed me was the range
of bundles including LaTeX. I'm also pretty new to LaTeX.
I have been using TextMate to render LaTeX with various engines
including XeTeX. It has been working perfectly on everything until now.
Now when I Apple+R to render I get the regular panel for a moment,
along with engine output/info, then it goes black but the spinner
stays. It "runs" forever like this. The behavior happens on any
engine and document content/size. The documents render to PDF fine
from TeXShop. None of that setup has changed. I installed the bleed
version of TextMate two days ago to see if it might fix it. No
difference.
What *has* changed in my setup is I installed the CS3 Adobe web suite
(a new paid/registered version, not warez) which includes Acrobat
Professional. I am guessing this has hooked/broken some PDF meta-info
somewhere.
Any pointers where to look to fix this? Acrobat includes an
uninstaller but I'd rather not do that. Is it something that can be
updated in the LaTeX bundle? I think this is likely since other LaTeX
apps are still rendering to PDF, only TextMate's behavior changed.
Thanks for looking at this!
-Ashley
Repost because the original message was garbled...
I've found a bug in the Ruby bundle for Textmate. Under certain
circumstances, using Control-Q to reformat comment code raises an exception
that spews error code into the source.
Is this the right forum to post bugs in Ruby bundles?
The problem occurs if you have a comment that contains a single word that
goes past column 79. For example, in the following code the x's in the
comment extend out to column 80:
#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
def func(x,y)
x+y
end
If you place the caret inside the comment and press control-Q you see the
following:
/Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:365:in
/bin/bash: +': invalid option
Usage: /bin/bash [GNU long option] [option] ...
/bin/bash [GNU long option] [option] script-file ...
GNU long options:
--debug
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--rcfile
--restricted
--verbose
--version
--wordexp
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o optionwrite'
from
/Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:408
def func(x,y)
x+y
end
This doesn't happen if the word in the comment stops before column 80.
This isn't an impossible scenario because it's easy to have a URL in your
documentation that's more than 80 characters long.
--
Bill McNeill
http://staff.washington.edu/billmcn/index.shtml
Lately, i've been experiencing various issues with the Rails Bundle:
- none of the generator tasks (controllers, models, migrations etc.)
work anymore. I just get an empty confirmation window and the tasks are
not run.
- when running any rake tasks, i get "stack level too deep" errors:.
For insatnce, here's the output from "Migrate to current" command:
RakeMate r6193
rake aborted! stack level too deep (See full trace by running task with
--trace) (in /Library/WebServer/railsapps/sparkle)
Done
Rake tasks and generator tasks work perfectly fine from the command line.
I'm using current Rails Bundle from trunk, but also tried the one that
came with the lastest TM release. I'm running on Leopard, Ruby 1.8.6;
projects are Rails 2.0.2, but it also seems to happen with Rails 1.2
projects.
Any ideas? Thanks.
Sebastian
Bummer, looks like Edit in TextMate… is not working properly from
Mail.app (or likely any WebView) since the Safari 3.1 install. The
content of the WebView is not transferred to TextMate. The MacVim folks
actually mailed me about it since they're using a modified version of
Edit in TextMate… with MacVim. Anyway, I won't be able to look into the
matter for a couple weeks in-case someone else wants to take a crack and
send Allan a patch.
j.
Hi all,
It seems the "Citation based on current selection" (Esc or Alt+Esc)
command doesn't show the entries of a .bib file that contain commas
in any field.
Example. LaTeX file with
\bibliographystyle{plain}
\bibliography{sample} % to get sample.bib
The entry (in sample.bib):
@book{knuth79,
author = "Donald E. Knuth",
title = "Tex and Metafont, New Directions in Typesetting",
year = "1979",
publisher = "American Mathematical Society and Digital Press",
address = "Stanford"
}
doesn't show up unless the comma in "title" is removed or replace by
another symbol such as _ (underscore).
TextMate 1.5.7 (1436)
Mac OS X 10.4.11 (PPC G4)
Cheers,
AgusN
Hi,
I've just migrated to Leopard, and I have the following problem.
If I drag'n'drop a pdf file from the Finder to a LaTex doc I get the
following error:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
1.8/pathname.rb:205:in /bin/bash: -c: line 0: syntax error near
unexpected token `('
/bin/bash: -c: line 0: `dup': can't dup NilClass (TypeError)'initialize'
from /tmp/temp_textmate.gqGtWt:7:in
OK. I went through previous mails regarding that issue, and I found
"update it". But what?
I'm using Textmate 1.5.7 (1455) on 10.5.2 (G5 ppc)
and
/usr/bin/ruby 1.8.6 (2007-09-24 patchlevel 111) [universal-darwin9.0]
Thanks for any hint in advance,
--Hans
Hi,
maybe this is a general issue.
I'm working a lot with bash/perl scripts. Sometimes I would like to
drag'n'drop a file from the Finder or from the Project Drawer to my
current document to only insert the relative/absolute file path plus
name. Up to now it is "only" possible to insert the content of that
file which is very useful. How about to use SHIFT drag'n'drop to
insert the relative file path and OPT drag'n'drop to insert the
absolute file path. Of course, the drag'n'drop commands specified in
bundles come first.
The only solution I found is to generate a drag'n'drop command, File
Types: *, Scope: empty, and handle the insertion stuff by myself.
--Hans
In the dialog after executing "Call Generate Script in Rails"
I think "OK" is more appropriate than "Ok" as the button label.
Takaaki
--
Takaaki Kato
http://samuraicoder.net
Thomas Aylott - subtleGradient wrote:
>
>
> I do recommend using Transmit with DockSend and the Transmit bundle
> for TextMate.
> Set it up properly and you can upload with a single action from
> inside textmate.
>
>
> —Thomas Aylott – subtleGradient—
>
>
Hi Thomas, thanks for the tip - I just found it on the forum archives. I'm
just getting started with TextMate and the Transmit bundle was just what I
needed. I have a small problem with DockSend though. I'm using Transmit
3.6.2.
Let's say my Transmit is already connected to my server, and my "Their
Stuff" is at the root level on the server. When I use DockSend to upload a
file that's in a directory within the root, say an img directory, it uploads
the file, but after it does so, I can't navigate to the img directory nor
any other directory within root. I always get this message:
http://www.nabble.com/file/p16265488/24cxhcn.png
where the blurred out part is the directory name I'm trying to open.
The only way to get out of it is to navigate to a higher-level directory
using the dropdown that's above the "My Stuff" directory box or to
disconnect. Once I can get to the location of the file, however, I see that
it's uploaded. If I'm DockSending to the root (the current directory my
"Their Stuff" is in), I can navigate to any other directory just fine.
It doesn't seem to be TextMate-specific (if I drag a file to the Transmit
icon on the dock I get the same error), but I can't find any Transmit forums
nor can I find the problem when I search for it. So I'm hoping maybe
someone on here has had this problem too. Maybe it's an outlier bug, but I
often have my Transmit window open and would rather not have to deal with
this every time I DockSend a file!
Thanks,
Annie
--
View this message in context: http://www.nabble.com/Remote-editing-of-projects-tp15053548p16265488.html
Sent from the textmate users mailing list archive at Nabble.com.
I recently recognized, that the control + escape shortcut to envoke
the gear menu doesn't work. Now I searched the archives, and found
that this question has come up before.
The only answer was, that it could be that the keyboard shortcut is
already assigned in the system-preferences.
Looked there, and it sure isn't.
I even created a new user and tried there, but even there it doesn't
work. Is this a known bug? Or am I just missing something?
running latest Leopard.
Thanks,
Thomas
Does textmate have an equivalent to emacs query replace that takes
term to search for, what to replace it with and then steps through
each match and asks if you want to replace or not
( moving view obviously to that area so you can view the code around
it )
?
hi, first post to this forum, after switching from BBEdit to TextMate.
while I'm discovering everyday the benefit of this change, I came
across a syntax problem with a Applescript I was using successfully
with BBEdit.
the principle of the script was to create folders and sub-folders,
then create a new document in one of them with my text editor, save it
with a title, bringing it to the front for entry.
changing the app to TextMate, I get an error:
[quote] AppleEvent Handler failed: expect end of line but get "to" [/
quote]
I have posted an entry on MacScripter, to hear that TextMate was
"poorly scriptable, even Standard Suite is badly implemented".
any solution to contradict that?!
below the script in question:
> set theFolder to choose folder with prompt "Create/Choose Client
> Project folder"
> try
> set briefFolder to ((theFolder as text) & "Brief") as alias
> on error
> tell application "Finder" to set briefFolder to make new folder at
> theFolder with properties {name:"Brief"}
> end try
> tell application "Finder"
> set capturesFolder to make new folder at theFolder with properties
> {name:"Captures"}
> end tell
> tell application "TextMate" -- was BBEdit
> set briefDoc to make new document at beginning with properties
> {name:"$.tasks"} -- was "$.todo"
> save briefDoc to ((briefFolder as text) & "$.tasks")
> end tell
> tell application "TextMate" to activate -- was BBEdit
--
cheers, Pascal
Hi,
We have a big problem in our society.
We updated to Leopard 2 weeks ago. Since, we have a LOT of kernel
panics when using TextMate (1.5.7 1455). Just for yesterday, I got 5.
It happened every time saving a file from TextMate on servers
connected via SMB (Windows or Linux servers). But not each time. All
our macs under Leopard are affected (10.5.2). We're trying to solve
this problem over the past week without success (desactivate IPv6,
uninstall BlueHarvest,…).
The problem does'nt happen with programs like Coda or CSSEdit, and not
on Tiger + TextMate.
Someone would have an idea?
Thank you
Tue Mar 18 13:36:08 2008
panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x0105624a, type
14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000010, CR3: 0x01504000, CR4: 0x00000660
EAX: 0x00000800, EBX: 0x00000800, ECX: 0x00000f80, EDX: 0x00000000
CR2: 0x00000010, EBP: 0x34d33558, ESI: 0x00000000, EDI: 0x34d33780
EFL: 0x00010206, EIP: 0x0105624a, CS: 0x00000008, DS: 0x34d30010
Error code: 0x00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x34d332a8 : 0x12b0e1 (0x457024 0x34d332dc 0x13321a 0x0)
0x34d332f8 : 0x1a8c8a (0x460550 0x105624a 0xe 0x45fd00)
0x34d333d8 : 0x19eb67 (0x34d333f0 0x34d33458 0x34d33558 0x105624a)
0x34d333e8 : 0x105624a (0xe 0x48 0x34d30010 0x1a0010)
0x34d33558 : 0x1058036 (0x78c1dd0 0x1 0x34d335c8 0x19d73a)
0x34d33578 : 0x1f1707 (0x34d3359c 0x0 0x34d335a8 0x1da8c3)
0x34d335c8 : 0x1f41dd (0x78c1dd0 0x34d33780 0xbd76484 0x385118)
0x34d33628 : 0x1db413 (0x78c1dd0 0x34d33780 0xbd76484 0x0)
0x34d338c8 : 0x356d8c (0x45ad550 0x0 0x80000002 0xbd76484)
0x34d33908 : 0x1d794d (0x45e5204 0x45ad550 0x80000002 0xbd76484)
0x34d33958 : 0x1c4d1a (0x78c1dd0 0x0 0x80000002 0xbd76484)
0x34d33f78 : 0x3dbe77 (0x4d8ea00 0xbd76380 0xbd763c4 0x13d1ed)
0x34d33fc8 : 0x19f084 (0xbd22240 0x0 0x1a20b5 0xbd22240)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb045a2e8
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.smbfs(1.4.2)@0x1040000->0x106ffff
BSD process name corresponding to current thread: TextMate
Mac OS version:
9C31
Kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008;
root:xnu-1228.3.13~1/RELEASE_I386
System model name: iMac6,1 (Mac-F4218FC8)
I've got both a personal MacBook, and a work MacBook pro, each with
licensed copies of TextMate.
A few weeks back on my personal machine, I followed the instructions
here to get Textmate to detect files ending in _spec.rb as rspec, and
just .rb as Ruby on Rails:
http://blog.macromates.com/2007/file-type-detection-rspec-rails/
I've just now tried to do the same thing on the work machine, and
while it detects rspec, Normal .rb files are coming up as Ruby rather
than Ruby on Rails.
The Ruby On Rails language has
fileTypes= { 'rxml', 'rb'}
as per the blog post (Yes I realize as I type this I need to make it
work with Rails 2.0 conventions).
When went looking in the Ruby language def to delete the file type
association to 'rb', there doesn't seem to be one.
Any ideas?
--
Rick DeNatale
My blog on Ruby
http://talklikeaduck.denhaven2.com/
(forgive my noobishness, I had to re-join the list after a long period
of inattention, and cannot respond directly to the original message,
from Thomas Aylott)
> Those few of you who care, please let me know what I need to do
> before I can replace the core bundles with these guys.
I was really excited to see activity related to JavaScript in /Review,
and I immediately switched my checkouts to track the JavaScript and
Prototype bundles in Review. The irony of someone who follows the
commit log feed yet had to re-subscribe to the mailing list is
exquisite, I know.
I've been using them for the past few weeks with few (if any)
noticeable problems, using the Prototype bundle as my chosen grammar
for *.js. That is, until today, when I decided to go poking about the
latest Prototype trunk.
The file generated by `rake dist` has _never_ been small, I'll grant,
but I don't recall so much chugging and whinging by my 2.2Ghz MacBook,
or seconds-long gaps of white syntax colorless-ness when switching
tabs (a beachball will occasionally pop up for a few seconds, even).
My wild shot-in-the-dark hypothesis is that it might be related to the
increased number of `include $base` declarations in the "new" grammar.
To reiterate, this only occurs on files like the `rake dist`-generated
prototype.js, which itself is over 4,000 lines of syntactically dense,
idiomatic (and often beautiful) JS.
There seems to be a regression in the regex literal highlighting, as
it no longer works when the RegExp literal notation is used as a
member of an object with any space separating the key's colon
delimiter and the literal itself. The literals are colored fine when
it begins on the very first character of the line, or when immediately
following a parenthesis. Line 275+ of prototype/trunk/src/selector.js
is a perfect example of this regression.
I narrowed down the cause of this anomaly to the 'string.regexp.js'
key of the Embedded grammar, specifically the `begin` regexp:
(?<=[=(:]|^|return)\s*(/)(?![/*+{}?])
The lookbehind seems to be blocking it; when I remove it, the RegExp
literals in the object values highlight as intended. This does cause
any single `/` to color everything after it as a regexp, but adding an
alternate end-of-line anchor ($) to the negative lookahead seemed to
fix that. (?![/*+{}?]|$)
There is also an oddity with the folding markers, which appears to be
related to the block comment syntax. Line 135 of prototype/trunk/src/
ajax.js:
'Accept': 'text/javascript, text/html, application/xml, text/
xml, */*'
Again, inside an object literal, but this time the "*/*" seems to make
the folding parser think "I need to start a new fold here!", when in
fact it is the last member of the object, and should have no folding
marker whatsoever. Take away the second * (thus turning it into a
block comment closing delimiter), and the folding marker disappears. I
was unable to parse the gargantuan folding regexps in the grammar
clearly enough to suggest a solution.
> The Review Prototype bundle is NOT upgraded for the latest version
> of prototype.
I'd be willing to pitch in on this effort, if you (or whomever "owns"
the bundle) would like. I've done a bit of local hacking on various
bundles, and I can certainly provide examples off-list. The Prototype
grammar itself could use a little cleaning up, I'm sure.
Big thanks to all the bundle contributors for continuing to make
TextMate great! (Oh, and Allan, too :D)
~ Daniel Stockman
evocateur.org
I'm currently using the Blogging Bundle to post to a WordPress 2.4
blog. I'm not entirely sure if the problem I'm experiencing is on the
WP or the TM side of things (or someplace in between), but it
manifests itself within (and so far, only within) TM, so I thought I'd
start here. If these questions would be better directed elsewhere,
please let me know.
After posting via TextMate, the post gets sent back down to TextMate
with various meta-data filled in. Among this meta-data is the date
field. This date is being offset back by 4 hours, although the actual
post within WP has the correct time.
For instance:
* I create a post within TM at 11:04:41 -0400, and post it to my blog.
* The post, within wordpress, has a post date of 11:04:41 -0400
* The post that's returned to TM, however, now has a Date of 07:04:41
-0400
This rollback appears to be directly related to the time zone as
defined in WordPress. If I change my time zone to NDT (-0230), then
the time that appears on the post inside TextMate is rolled back by
2.5 hours:
* I create a post within TM at 11:04:41 -0400, and post it to my blog.
* The post, within wordpress, has a post date of 11:04:41 -0400
* The post that's returned to TM, however, now has a date of 08:34:41
-0400
The issue is that if I then update the entry and repost via TextMate,
I need to manually adjust the time on the entry, or it will now be
back-dated within WordPress as well. I frequently revise posts after
they've been published, and depending on the time of day, this
behaviour can even result in my permalinks being changed.
I also downloaded another blogging client (MarsEdit), and attempted to
re-create the problem there. Other Blogging Client displays the same
date/time as is stored in WordPress; reposting the entry does not
cause the date/time in Other Blogging Client to change.
Which leads me to suspect that the problem is somehow specific to
TextMate or the Blogging Bundle.
I'm running TextMate Version 1.5.7 (1455) if it matters. I'm not sure
which version of the Blogging Bundle I'm using, as it doesn't seem to
advertise that anywhere that I can see.
My thanks in advance for any pointers or suggestions anyone may be
able to offer.
Gwen
Hi,
I do not know whether this is interesting for other users as well,
but I find it's worth to have a small note on it.
Up to now TM doesn't have the chance to do something when it starts.
But there is an easy way to trigger a tmCommand or whatever.
A concrete example:
I want to open TM and it should start Rdaemon automatically.
Solution:
I wrote a tiny AppleScript with Script Editor:
tell application "TextMate"
activate
tell application "System Events" to keystroke "r" using {control
down,command down,option down}
end tell
and I save it as an application with the name "TM_Rdaemon" (if you
want, customize the icon ;). Now you put this app to any location or
drag'n'drop it to the Finder's toolbar.
If you invoke TM_Rdaemon.app it starts TM and it executes the key
combo CTRL+OPTION+APPLE+R which is a shortcut to open Rsession.proj
and to start Rdaemon.
To generalize it a bit one can also use this simple approach to
trigger a auto-start-up script. The only thing to do is to create a
tmCommand, let's say AUTOSTART, with the desired commands you want to
call after TM started and bind it to a UNIQUE key combo without
setting a scope.
After doing it, change the above mentioned AppleScript and
change ...to keystroke ... to your UNIQUE key combo.
Then you can change the AUTOSTART tmCommand easily to trigger some
stuff, e.g. open the Bundle Editor and open a specific project or
whatever; or open a file and set it to specific grammar language.
Everthing is done by using AppleScript's '"System Events" to keystroke'.
At least for me, it saves sometimes a bit time.
[BTW Is this worth to mention it in TM's wiki "How to > AppleScript" ?]
Cheers,
--Hans
I have a question about comment blocks in Java and possibly a bug with
the scope.
consider this (foo.java):
/**
* This class interfaces with the native Cpp Library to model a jet
engine.
* It provides methods to set input parameters and retrieve the state
of the
* engine via a list of output values.
*
* @author Thomas Krajacic
* @version 1.0
*/
when I put the cursor somewhere inside the first paragraph and select
from the menu
Edit > Select > Current Scope
The selection is missing the first 'T' and starts with the 'h'.
Anyway. There used to be this little command called "show current
scope" but I can't find it anymore.
Is it gone? I saw it in one of the first screencasts. (The shortcut he
used was Ctr-Shift-P, but typing that
actually performs the same thing as Shift-UpArrow... just selecting
the line from the cursor back to one line above)
Furthermore there was this episode [Scope Based Customization] where
Allan showed
the snippet to make returns inside a comment block automatically
insert an asterisk at the beginning of the line.
This has not been implemented yet? (Still something to create
yourself? Admittedly really simple but still...)
I already suspect that I have somewhat of a corrupt Textmate Bundle
maybe because I can't find those things.
I use the svn checkout to get the latest bundles and in my users
library/application support, there is no
Textmate Bundle that would override the checked out version.
Maybe someone can try the selection thing out and shed some light on
the snippet inexistence for me.
Thanks,
Thomas
Hi
I'm writing a Bundle to integrate RubyStacks in TM, the first release is
almost finished. However, I'm stuck with one feature:
One of the bundle commands is supposed to start mysqld. It's working so far,
but mysqld does not detach from the process and thus the (Ruby) script hangs
TM until killed. I've tried all kinds of things like calling it in backticks
`/path/to/mysqld`, or forking/detaching, even `nohup /path/to/mysqld &`. No
matter what I do, mysqld doesn't detach from the script launched from within
TM.
Any ideas why?
Thanks, -sven
--
View this message in context: http://www.nabble.com/Starting-mysqld-from-Bundle-tp16117091p16117091.html
Sent from the textmate users mailing list archive at Nabble.com.
Why is this not working for me?
When I use a \ref{} and press escape nothing happens except a sound
from the computer.
How can I track down the problem?
Christopher
*****************************************************
Department of Computer Science, University of Sheffield
Greetings list members,
Does anyone have any applescripts or information on enabling tiling
and cascading TextMate windows? I'm hoping to find someone on this
list who has a simple expedient or barring that finding out that it
isnt currently possible. Then take it from there. Thanks all~
~James
On Mon, Mar 17 Mar 2008, at 16:33, Hans-Joerg Bibiko wrote:
> I changed the code for it a bit in that respect.
>
> Now you can select the function declaration and send it to the
> Rdaemon, switch to the Rdaemon doc, and you can use that function
> (the Rdaemon console is not "messed up", error messages could be seen
> with opt+apple+A 2).
> ...
> Of course, if there is a need to have also/only the "old" behaviour I
> can add/change this. Any comments?
Ah, I see. Interesting approach. I do like that in some circumstances.
Other times, however, it is nice to get some immediate feedback on
errors and/or R output when sending selections of text to Rdaemon. I
guess the disadvantage is that you can't have multiple console windows
open without consequences. (Although I've never found myself doing
that.)
Might be nice to simply have two bundle commands: one to send silently
and one to update the console and output the result.
This new behaviour reminds me of the Emacs + ESS command 'evaluate
this line/region' without switching focus. On that note, as an
alternative, would it be possible to have a selection sent to the
console, the output displayed, and the focus shifted back (or always
staying on) the R source code window? I would find that quite useful.
Thanks for all your work!
Sean
