I don't know of a graphical IDE with the features you want. What's so intimidating about typing text into a black window instead of a white one?
It is hard to compare code when you have multiple windows open.
---------- Post updated at 05:39 PM ---------- Previous update was at 05:37 PM ----------
Quote:
Originally Posted by DGPickett
I was playing around in Eclipse trying to get the C++ plugin to work, so I would have one IDE for both JAVA and C++. Maybe it will work for you!
The diff has some very nice optional presentations for comparison. I like the one where lines are prefixed =+- for same, new, old. I also love diff3 -e to merge changes from a common starting point file and two modified files using ex.
A coding style with many lines really helps all tools, so start designing, and adhering to, a nicely indented, one line per parameter, assignment or boolean predicate style. Alas, comma lists and other infix operators mess this up a bit with list-level operators intruding into the list elements, unless you go newline-crazy-ugly (I've seen it)!
Oh, for a language with lists externally notated, like:
Before I learned how wonderfull VI and Unix was. I used a little crappy DOS editor. I wouldn't go back to it for anything. However I work with a lot of formatted files that use the column position. I wonder if any here knows of a way to make VI display the cursors coulmn position or if there is a... (2 Replies)
I currently use konsole fo rmy terminal use.
when i go into vi and type the letter t the stupied thing highlights the letter brown and it messes my thing up. Whereever i type the letter t it highlights in brown. Is there some way to change it. I dont know how this problem start. RH 8 (3 Replies)
Hello,
I enjoy using the unix screen utility, but my vi sessions lose the ability to syntax highlight code and split screen(:vs or :sp). When not using screen, I can do those things within vi. Anybody experience this and know the fix?
Thanks (1 Reply)
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Wellcomes All,
some times ago I 've installed a Debian ditribution on an Hard Disk who was set as Primary Master. Few days ago, I 've decided to install another Hard Disk with a different Operating System. When I did that, I turned off the old hard disk, and I mouted the new one on the Primary IDE... (1 Reply)
Hi,
I want to create a text editor in C on Unix. Can any1 jus tell me how to start with n wat all I have to look into if I have to write an editor..
Thanks (2 Replies)
I have a text file with entries like
1186
5556
90844
7873
7722
12
7890.6
78.52
6679
3455
9867
1127
5642
..N so many records like this.
I want to split this file into multiple files like cluster1.txt, cluster2.txt, cluster3.txt, ..... clusterN.txt. (4 Replies)
Discussion started by: sammy777
4 Replies
LEARN ABOUT DEBIAN
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS --debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)