On Tue, 2004-03-30 at 17:33, Eric G Ortego wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alvaro Zuniga wrote:
>
> | I am thinking about adding drag and drop support under gnome. This
> | would
> |
> | make a great difference for me. I usually have three copies of the
> | editor running and three or four nautilus windows. I find it a lot
> | more comfortable to drag and drop the file.
>
>
> you should try out rox-session, almost everything has a drag and drop
> interface.
I will give that a shot, never heard of it. I will read about it soon as
I send this email.
I am pleased with GPHPEdit and I have been using gnome for a while. I
just would like to have drag and drop and maybe modify the class browser
so that it does not parse functions but limits itself to methods. The
functions I would like to have them displayed on a drop down similar to
Anjuta.
> |
> | Class Viewer is not available in vi.
>
>
> have you tried develop? It can have vi as an editor and also has a class
> viewer. :-)
> How's that for modularity?
Its like those Macintosh emulators where you could run windows on top of
it. This analogy is true in two ways: vi is big so I am not sure about
the modularity but what true for sure is that much like windows I run
away from vi.
>
> | But my dislike with vi is not a matter of its features really.
> | WhatI hate is the what you need to do to save and even search.
>
>
> search is /stringtosearchfor
> this works in mozilla as well.
> I don't think I can understand your frustration with :w
Simple, you are editing and you can not save your current work like the
standard ^s, copy routines with the standcart ^xcv.
You have to get to editing mod by going all the way to the scape key,
Then press shift-colon, then w, then i ( usually you want to stay where
you are ).
Other editor you press ^s and you are done. And what is even more ironic
is that the combination of ^s puts vi in what is an unknown state to me,
someone once told me but I forgot.
Now, do not get me wrong about something. If I need to do work in a
terminal this has been my editor of preference because some UNIX book
once said I should know how to use it. I have been was testing out nano
but it does not seem to handle large files to good. Sometimes I have to
deal with mysqldump files and those get really large sometimes. Even vi
chokes of the files sometimes. Also key strokes are not standard in
order to keep compatibility with pico for some unknown reason. I suppose
I could remap the keystrokes. Maybe yet another project for the future.
> | When I was referring about the far away keys is not that it is only
> | one key but multiple keys at opposite locations of the keyboard.
> | Those I believe are the most basic functions of any editor.
>
>
> I don't know about you but typically I can press 2 keys on different
> sides of the keyboard faster than I can 2 on the same side.
don't you have two control keys :-)
This is something that I have always love of the mac environment. It is
difficult to do control-anything because you have to use your pinky. On
the macintosh however, most of this tasks are assigned to the Alt key.
This make a great difference.
> |> vim can do code folding too you know. You can create named
> |> markers, named buffers, move named buffers to named markers, jump
> |> between named markers.... soo many things... And its fast, in a
> |> screen session, xterm, console, across a 14.4kbps satelite phone
> |> at $10 a minute(how much data would you want to move), vim rocks.
> |>
> |>
> |
> |
> | It probably requires magic to make them work.
>
> not at all, just a few simple keystrokes.
> markers can be named {a-z}{A-Z}
> ma
> sets the position under the cursor to a marker named a
> 'a
> goes to marker a
>
> most buffer commands begin with :b
> you can create buffers in swap and set them as readonly, many many
> neet things to be done with buffers.|
> You can add a file to a buffer without "opening" it
> :badd file.txt
> :badd file2.txt
> That will add two new buffers to the buffer list.
> to view the buffer list
> :ls
> to delete a buffer
> :bdelete 2
> or
> :bdelete file.txt
>
> edit the buffer? :b2 or :2b
> buffers rock.
>
>
> most the folding functions start with z
> bah Im getting lazy...
> :help fold
>
> All of this is simplified even more in the gui enabled version of vim.
>
> | Would you not like this knowlege to transfer to other applications?
> | Kind of like Perl and Posix regex.
>
>
> You don't want _my_ opinion of perl.
> I find alot of applications use the same keystrokes as vi.
> Like my mozilla refrence above. Also irssi, and screen share some
> keystroke similarities. I'm sure there are others I just don't recall atm.
>
> | All I meant to say is that if you forget to do su, as soon as you
> | try to edit a file you get the notice that the file is read only.
> | Then you have to exit vi and su and then start it again. With pico
> | or nano this will be a lot more confortable because there are less
> | commands.
>
>
> How do I chmod or overwrite a file owned by another user in nano or pico?
I do not know but you I do not think it is possible. This is what I
mean: I never use the root account unless I have to. I decide to change
something to some /etc/ file. I often forget I am not root and attempt
to edit the file. Soon after typing the first letter I get a notice by
vi that it is read only. I exit the vi editor, I become root, and then I
reopen the file.
What I am trying to say is that in pico I do ^X and then say no about
writing the file.
( control possibly with your left pinky, x, then n then enter )
In vi, exit editing mode, then :q!
( esc all the way to the upper corner, then shift key probably with the
left pinky, then colon probably with the right pinky, then w then q then
shift with the left pinky and then ! and then enter )
This alone is why I hate vi, it is used so often that it is enough of a
pain to me.
then back to the file, pico /etc/asdf.conf and you are in business.
but not in vi, you have to vi /etc/asdf.conf and then press i or
whatever.
My comment has nothing to do with permissions.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFAagPW6JFKsKsJemQRAmqiAJ0aU40Z8fxHZefsz1kTth2PWuL6jwCgp2yb
> f9NrH+iyG2OmMGeiJzITizM=
> =AFbX
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> General mailing list
> [email protected]
> http://brlug.net/mailman/listinfo/general_brlug.net
