Hello,
"fnegroni" <[EMAIL PROTECTED]> wrote:
> [...]
> I am about to embark in developing such feature for vim and will make
> it available as a patch, if there isn't one already available.
Have a look at the two local_vimrc plugins on sourceforge. They already provide
this feature.
I'm not sur
On Tue, Aug 26, 2008 at 15:11, Paul LeoNerd Evans
<[EMAIL PROTECTED]> wrote:
> I did consider some stripped-down way of specifying just a few known-safe
> settings. But I'm not sure I like that as a solution.
This is what modelines do (and even there, there are some arguments).
As pointed out l
On 26/08/08 15:11, Paul LeoNerd Evans wrote:
[...]
> Similarly, I like to allow the possibility of arbitrary code in
> such .vimrc files. Perhaps my company's style guides require 4 space
> indents in code written on Tuesday, and 3 every other day? Silly I know;
> but if you can allow that sort of
On Aug 26, 1:45 pm, Paul LeoNerd Evans <[EMAIL PROTECTED]> wrote:
> On Mon, 25 Aug 2008 14:45:24 -0700 (PDT)
>
> fnegroni <[EMAIL PROTECTED]> wrote:
> > I am about to embark in developing such feature for vim and will make
> > it available as a patch, if there isn't one already available.
>
> I wr
fnegroni wrote:
> There is a feature in Perforce, which allows the command line client
> (p4) to find its configuration file (.p4rc) by looking up the current
> directory and any directory above it in recursive order, stopping at
> the first one that has a .p4rc file in it. If that fails, it falls
On Tue, 26 Aug 2008 14:01:12 +0100
"Jan Minář" <[EMAIL PROTECTED]> wrote:
> Let me ask: What are the commands you (would)
> put in that .vimrc? What are the problems you are trying to fix?
I find it's usually stylistic issues. Quite often I'll be changing things
like shiftwidth, expandtabs, som
On Tue, 26 Aug 2008 14:01:12 +0100
"Jan Minář" <[EMAIL PROTECTED]> wrote:
> This is inherently insecure.
I am aware of this; I make it very clear.
Drop a .vimrc saying
let g:additionalrc_stop = 1
in the innermost-nested place you can that's still safe, and all is OK.
Fail to do that, and On
On Tue, Aug 26, 2008 at 1:45 PM, Paul LeoNerd Evans
<[EMAIL PROTECTED]> wrote:
> On Mon, 25 Aug 2008 14:45:24 -0700 (PDT)
> fnegroni <[EMAIL PROTECTED]> wrote:
>
>> I am about to embark in developing such feature for vim and will make
>> it available as a patch, if there isn't one already availabl
On Mon, 25 Aug 2008 14:45:24 -0700 (PDT)
fnegroni <[EMAIL PROTECTED]> wrote:
> I am about to embark in developing such feature for vim and will make
> it available as a patch, if there isn't one already available.
I wrote one:
http://www.leonerd.org.uk/hacks/vim/additionalrc.html
--
Paul "Le
On Mon, Aug 25, 2008 at 5:45 PM, fnegroni <[EMAIL PROTECTED]> wrote:
>
> There is a feature in Perforce, which allows the command line client
> (p4) to find its configuration file (.p4rc) by looking up the current
> directory and any directory above it in recursive order, stopping at
> the first o
fnegroni wrote:
> It is a feature that I would absolutely love to have: I
> develop for several projects following different indentation
> styles and visualisation rules.
Some code in your vimrc to detect the current directory at startup, then
implement
the wanted settings, might be easier.
O
There is a feature in Perforce, which allows the command line client
(p4) to find its configuration file (.p4rc) by looking up the current
directory and any directory above it in recursive order, stopping at
the first one that has a .p4rc file in it. If that fails, it falls
back to the one in the
12 matches
Mail list logo
