On Nov 28, 2013 5:27 PM, "Ed Kostas" <edu500ac@gmail.com> wrote:
>
> On Thursday, November 28, 2013 8:39:02 AM UTC-2, Ed Kostas wrote:
> > I am helping a lawyer office in (a difficult) trying Vi(m), and have a few questions. The fact is that Vim seems to be very slow compared to Emacs. Let me elaborate on that.
> >
> > 1 - Lawyers work with long (very long) texts and Latex sources. Basically, an OCR program transforms every thing they are working with into text. Asterisks are added automatically by the OCR, that is written in Lisp (or inLab Scheme). The asterisks control the outline in something lawyers call org-mode. They use tabs and shift tabs to close the outline, and have a fast overview of the document.
> >
> > It seems that Vim outline did not work as well as Emacs Org-mode. The lawyers complain that it takes forever to close or open the paragraphs. It does not have schedules, calendars, deadlines, etc. Latex sources seems to be much slower in Vim, and often freezes Vim. In fact, I noticed that Vim becomes so slow that people types faster than Vim deals with the syntax coloring. First question: How to make Vim faster?
> >
> > 2- Lawyers often make search by meaning. There are programs, in elisp, that analize the text, and perform a fuzzy search. Second question: How to switch from vimscript to Lisp? Any dialect if Lisp will do. People who wrote the scripts said that they can convert everything to Racket, Common Lisp, etc. I read somewhere that Vim accepts scripting in almost any language: Python, Ruby, and Racket.
> >
> > 3- It seems that there is a Vi clone that does everything these lawyers want. It is fast in dealing with large Latex sources, it has an org-mode that works like emacs, etc. etc. It is called Evil. Third question: What am I loosing if I work with Evil?
> >
> > Please, I am not a programmer expert. In fact, I know very little about programming, and almost nothing about Vim and other Vi-clones. People says that Vim is better than Emacs, and that everybody uses Vim, etc. Therefore my friends decided to give Vim a chance. Audiatur et altera pars, lawyers say. In the context, it means: If there is a claim that Vim is better than Emacs, you should try Vim, before dismissing the claim. Therefore give examples, and explain how to install everything that need to be installed in order to make Vim faster.
>
> To Marc Weber.
>
> Thank you for your prompt answer. I am very impressed with your knowledge of the problem. I thought nobody heard about org-mode, and you came with an alternative :-)
>
> 1- Speed. I followed your recomendation of turning the syntax off, and it worked in the sense that Vim became faster.
>
> :syn off
>
> However, the syntax colors disappeared. I am sure that you expected that. You probably wanted to check whether the problem was with the syntax highlighting. As for the version, people are using the 7.4 version, that one installs with mercurial. Thus:
>
> ~/edt# hg clone https://vim.googlecode.com/hg/ vim
>
> Then then they (the lawyers) compile it with:
>
> ./configure
> make
> sudo make install
Not much useful unless you know when exactly did they do this.
Also using "make install" is considered a bad practice for any distribution. It does not do something like rendering vim unusable, but maintaining jobs (like updating software on machine) will become such a pain in ass if you have packages installed like this.
> I read in the site that one should also type:
>
> hg pull
> hg update
>
> They have skipped this step.
Doing this (or "hg pull -u" which will do both at once) does not make much sense just after you did "hg clone". It does make sense if some time passed before one did "hg clone" and started compiling vim.
>
> 2) I am glad to know that I can compile Vim with Racket. This solve the other problem too. I will start looking for documentation on how to do it. I would appreciate if somebody know how to do it, and could provide a command line to build vim with Racket. Is it as easy as building vim with Python?
Last time I checked (guess at least a year ago, maybe several years) it was crashing on mzeval(). It is very unpopular language to compile vim with.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment