 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New schrieb:
> Yet everything I've heard, people like it much better after actually
> using it for a day.
It's a PITA though if your main job involves only occasional use of
Office, and you have the old stuff at home... That sucks.
>> That's why I prefer vi and emacs: solid, well-grounded 30+ years
>> interface
>> design... ;)
Yuck^2 !
You can only learn to love *that* interface if you're locked up in a
room with no more than a Linux computer locked down in such a way that
the only way of interacting with the outside world is via the vi
interface - for a *month* at least!
Even then, I suspect it will cause mental defects and emancipate dental
fillings in semi-rare cases :-P
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
clipka wrote:
> Darren New schrieb:
>> Yet everything I've heard, people like it much better after actually
>> using it for a day.
>
> It's a PITA though if your main job involves only occasional use of
> Office, and you have the old stuff at home... That sucks.
Well, switching back and forth is annoying, but if it's only occasional use
it's really not that much of a problem. It's not like one memorizes
keystrokes as in vi or emacs.
This is exactly my situation, and it's really not a problem.
> You can only learn to love *that* interface if you're locked up in a
> room with no more than a Linux computer locked down in such a way that
> the only way of interacting with the outside world is via the vi
> interface - for a *month* at least!
Ehn. I learned vi back when emacs' execution size was bigger than the
address space available in real mode and vi would run in 64k. :-)
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New wrote:
>
> Yet everything I've heard, people like it much better after actually
> using it for a day.
Having it installed and used for something like 2 months hasn't been
enough for me. The basic idea seems to work, but there are options that
I just can't find (eg. security level for running macros in Excel).
I'm not a heavy user on MSO, though, but when I use it, I usually do
something normal users don't...
-Aero
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
clipka wrote:
>
> You can only learn to love *that* interface if you're locked up in a
> room with no more than a Linux computer locked down in such a way that
> the only way of interacting with the outside world is via the vi
> interface - for a *month* at least!
>
> Even then, I suspect it will cause mental defects and emancipate dental
> fillings in semi-rare cases :-P
After having to use Vi for couple of hours, I even efforted to find
Vi-compatible editor for Windows to use at work. It's just so fast and
practical - somehow <esc>:w! is faster than ctrl+s for me (technically
it should be just the opposite).
http://www.winvi.de/en/download.html
-Aero
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Eero Ahonen wrote:
> After having to use Vi for couple of hours, I even efforted to find
> Vi-compatible editor for Windows to use at work.
"GVIM" is the usual answer to this. http://www.vim.org/
That's probably just the most widely used version, and it's the same "vim"
as on Linux and all that. Lots of good extensions over standard vi, while
still being finger-compatible.
> It's just so fast and practical
The one thing I missed most when I was using emacs was the "." command.
In any case, just so you know, vi vs emacs arguments are a classic flamefest.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Eero Ahonen schrieb:
> Having it installed and used for something like 2 months hasn't been
> enough for me. The basic idea seems to work, but there are options that
> I just can't find (eg. security level for running macros in Excel).
Maybe because 99.999% of all users never search for that /anywhere/, so
that's exactly where they possibly placed it...? :-)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Eero Ahonen wrote:
> I just can't find (eg. security level for running macros in Excel).
I just fired it up, hit F1, and typed "security level for running macros".
I got an entire tutorial on it, including how to sign code and links to
things like "how to turn off security warnings permanently" on other pages.
I'm guessing you're missing the developer tab, which you have to explicitly
turn on according to the docs.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
clipka <ano### [at] anonymous org> wrote:
> Darren New schrieb:
> > Yet everything I've heard, people like it much better after actually
> > using it for a day.
>
> It's a PITA though if your main job involves only occasional use of
> Office, and you have the old stuff at home... That sucks.
>
> >> That's why I prefer vi and emacs: solid, well-grounded 30+ years
> >> interface
> >> design... ;)
>
> Yuck^2 !
>
> You can only learn to love *that* interface if you're locked up in a
> room with no more than a Linux computer locked down in such a way that
> the only way of interacting with the outside world is via the vi
> interface - for a *month* at least!
It was an obvious joke. :)
In any case, I learned vi(m) about 4 years ago and decided to drop emacs
altogether. It's an incredibly full-featured and easy editor once you get past
the initial fear. Specially when combined with ctags.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
nemesis wrote:
> Specially when combined with ctags.
I could really use a ctags that works with C++ these days. :-(
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> nemesis wrote:
> > Specially when combined with ctags.
>
> I could really use a ctags that works with C++ these days. :-(
http://ctags.sourceforge.net
never heard of it until seeing it recommended in the vim manual... truthfully
highly recommended! :)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |