Is there any way to clear a Rebol console? (Maybe there are too many things in the console and I don't want to open a new one ;-) or I need to print some things in a clear console).
I know we can call cls in Windows or clear in Linux to clear the console. But how can I do it in Rebol, just in console or some script files?
In Rebol, I know we can do a system call with something like call "cmd". But call "cls" doesn't work.
This works also with
print "^L"
and there is a complete terminal control dialect available
Here is an answer that works with Rebol 2. I haven't taken the plunge to R3 yet.
print "^(1B)[J"
This reference to rebol console commands might be helpful.
http://www.rebol.com/docs/core23/rebolcore-18.html
In my systems simply hit Ctrl-L. But may depends on terminal....
Related
0.7 warns to use revise.jl, but on its documentation I just can't find a command to just say "clean it all".
Yes, I can sure just restart Julia, but in an IDE is several clicks away, while sometimes I just want to clean all variables/modules previously defined..
Yes, I can sure just restart Julia, but in an IDE is several clicks away
Assuming you are using Juno,
press Ctrl+j then Ctrl+k.
Docs
This kills the julia process, which will then automatically restart.
It is fairly fast
One possibility is to work with your code inside a module MyModule, then use Atom/Juno's inbuilt ability to define the working module in the left-most part of the bottom bar. Reevaluating the module should clear everything.
You can add this to your startup.jl file, and workspace() should work essentially the same as on previous Julia releases:
function workspace()
atexit() do
run(`$(Base.julia_cmd())`)
end
exit()
end
Say I enter the following commands into the console in Rstudio
x=seq(0,1e11, by=.01)
plot(x,sin(x))
Clearly this is a very silly thing to do. But my question is how do you terminate this process? I couldn't find this answered anywhere.
Attempted solutions: pressing ctrl+q, pressing esc, going to session->interupt R, going to session->terminate R. Nothing seems to work. This seems to be specific to plotting, for example if you run a stupidly large loop, most of the above options seem to work as expected.
Ideally I'd like a solution that doesn't lose the R script I have been working on in the console (as I haven't saved it in awhile).
Re-posting my comment as an answer since it seems to have solved your problem.
Save early, save often, cry less.
Try clicking the little red
stop icon above the console panel (unlikely to work if you've done
all that you've done already).
Try copy/pasting the script out to
a text editor.
Try killing just the rsession process through your
OS (might leave RStudio open). The good news is that RStudio is
often pretty smart about backing up working copies of scripts, so
you might find it's still there even if you have to kill the whole
program.
Entering dev.null() in the console will kill any plots and I find it's less likely to crash RStudio than some of the options given by Ari B. Friedman.
That said, save early save often is always sound advice.
Rstudio has a great code completion feature. It provides a quick view of functions that start with a given string, as well as function and parameter definitions.
ESS is powerful enough, familiar to me, and integrated into Emacs, where I conduct most of my work - so I am hesitant to move, but this feature is making me consider such a move.
Is it possible to integrate this feature into Emacs ESS?
Is there anything similar to this for Emacs ESS?
Any hope that there will be (and if so, how could I support such an effort?)
You do get the completion thanks to the rcompgen package by Deepayan (now "promoted" into base R as part of the utils package). So when I type
lm(
and hit TAB a new buffer opens which gets me the left-hand side of your window above: the available options to the function at hand. I don't think you can show the help directly though.
There is / was also a way to get context-sensitive help in the mini-buffer when typing but I have forgottten how/where that gets turned on.
[EDIT: This is an old answer and auto-complete package dropped out of fashion since then. Please use company-mode instead. It should work by default. Wiki configuration entry is here.]
Recent versions of ESS (> v.12.02) integrate with auto-complete package out of the box (you need not configure anything, just install auto-complete). It provides help on arguments as well as function help. I added detailed instructions to the wiki
Ess-eldoc was also rewritten and from v.12.02 it's active by default, so you don't need to configure anything.
Or maybe we should all use search:
Emacs autocomplete-mode extension for ESS and R
I don't want to be grumpy, I found this few hours ago and I'm still shocked. It works like a charm. Though I still prefer the old-style pop-ups. =)
I have been using UNIX for years and the dcop command only recently came to my attention. What is its primary purpose and is using it in any process a sign of poor design?
is using it in any process a sign of poor design?
Probably not, as long as you're using DCOP to perform some task that would ordinarily be done with a mouse click or hotkey. It's certainly way better design than trying to control the mouse to do what you want to do with the program!
But if you use DCOP to do something really simple that could be done directly with a shell command or a few lines of C code, without invoking a KDE application at all, it's probably better to just do it the direct way. (e.g. don't use DCOP to tell Konqueror to remove a directory tree, just run rm -rf)
I suspect it mainly exists because everything in UNIX ought to be accessible from the command line.
The Wikipedia article on dcop is worth a read.
It's great for any scripts to use to control processes, there's also good information on controlling Amarok via dcop.
Can anyone recommend a good (AS3) logging API for Flash/AIR/Flex? I need something to capture and record mouse and keyboard events in addition to coded events. Preferably something well documented/supported. Thanks in advance.
I've been using Thunderbolt. It allows you to see your log results in Firebug.
I developed and manage Loggee!, a Flash/Flex Logging Tool: http://davidbuhler.org/loggee-flex-logging-tool/
You must see http://sourceforge.net/projects/log4flash/
with no more....
bye bye
I would recommend Arthropod if you are looking for a development tool (this wasn't very clear in your question), if it's to log your client's behavior, I'm not aware of any tool sorry.
I always end up writing my own logging solutions. They generally are very simple compared to the rest of the project, and by writing my own I can tailor it exactly to what I need. Whereas using a pre-built one, always seems like either it is too over-engineered and complex to use, or it's too simple and lacking a couple features I need.
Try to use Log5F logging utility for ActionScript 3.0