On Tue, Jan 09, 2007 at 10:23:25AM +0100, Bram Moolenaar wrote:
>
> Dave Land wrote:
>
> > On Jan 8, 2007, at 3:03 PM, Dave Land wrote:
> >
> > > Happily, Apple provided a utility that handles it for you:
> > >
> > >defaults read "${HOME}/.MacOSX/environment"
> >
> > Actually, making this w
litespeed59 wrote:
Robert,
Yes, the initial Subversion download will get Vim with all the latest
patches. There may be a delay of a day or two between the time the patches
are first released, and when they appear in the Subversion repository, but
otherwise this is a great way to stay up to date.
Robert,
Yes, the initial Subversion download will get Vim with all the latest
patches. There may be a delay of a day or two between the time the patches
are first released, and when they appear in the Subversion repository, but
otherwise this is a great way to stay up to date.
Regards,
Trev
Ro
Hicks
Sent: Friday, January 19, 2007 9:33 AM
To: vim@vim.org
Subject: Re: Mac Questions
When you do this "--enable-pythoninterp --enable-rubyinterp" what do you
get? Does that just allow another language to be used as a "vim script"?
Robert
litespeed59 wrote:
Alan,
I recently figured out how to compile Vim on a Mac from source, so here is
the method I used. I too am fairly new at this, so if any Mac users can
improve on my instructions, feel free to do so.
I obtained the Vim sources through Subversion (I keep my source code
downlo
When you do this "--enable-pythoninterp --enable-rubyinterp" what do you
get? Does that just allow another language to be used as a "vim script"?
Robert
Alan,
I recently figured out how to compile Vim on a Mac from source, so here is
the method I used. I too am fairly new at this, so if any Mac users can
improve on my instructions, feel free to do so.
I obtained the Vim sources through Subversion (I keep my source code
downloads in ~/Source). Yo
On Mon, Jan 08, 2007 at 06:35:18PM +1100, Brett Calcott wrote:
> I thought the same thing. But it does not appear to source my
> .bash_profile or .bashrc.
Why would it? Vim is not bash.
The shell in which you run a console vim should have already sourced bash
startup files as appropriate (see th
On 2007-01-12, at 03:45, A.J.Mechelynck wrote:
By default, Vim doesn't change directories when you open a file. If
you open Vim from the Dock, without a filename, the current dir is
your home directory. If you later edit one or more files, the
current directory is unchanged. If you want
Alan G Isaac wrote:
On Mon, 8 Jan 2007, Brett Calcott apparently wrote:
I have just got a Macbook (switching from windows) and
have downloaded and compiled the latest version of Vim on
it. It all works fine, but I have a few questions.
Would you mind outlining the steps you took for someone
Timothy Knox wrote:
Somewhere on Shadow Earth, at Fri, Jan 12, 2007 at 03:45:26AM +0100,
A.J.Mechelynck wrote:
Alternately, you can use
:autocmd BufWinEnter * lcd %:p:h
which will set a "local directory" for each buffer. This alternative only
requires +autocmd, which is included in
Somewhere on Shadow Earth, at Fri, Jan 12, 2007 at 03:45:26AM +0100,
A.J.Mechelynck wrote:
> Alternately, you can use
>
> :autocmd BufWinEnter * lcd %:p:h
>
> which will set a "local directory" for each buffer. This alternative only
> requires +autocmd, which is included in "Normal", "Bi
Krzysztof MaJ wrote:
[...]
Hi,
I have a question. If I open my GVIM from the Dock and after that I open
some file from the gui it sets PWD to my home directory not to the place
from the file really is. If I open the same file clicking on it in
Finder VIM sets PWD to the right place (to directo
On 2007-01-09, at 14:54, Brian McKee wrote:
" Get a good value for $PATH. For example, if teTeX is installed,
this
" should add the path to tex, pdflatex, etc.
" This should only make a difference when vim is started from the
Finder or
" with open.
let $PATH = system("printenv PATH")
let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8-Jan-07, at 6:14 PM, Dave Land wrote:
On Jan 8, 2007, at 3:03 PM, Dave Land wrote:
Happily, Apple provided a utility that handles it for you:
defaults read "${HOME}/.MacOSX/environment"
Actually, making this work in bash (or other shell)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8-Jan-07, at 5:31 PM, Brett Calcott wrote:
This does seem to be the case. No amount of fiddling with .profile
.bashrc .bash_profile /etc/bashrc or whatever makes any difference to
the environment that ends up in the GUI version that is started fr
Dave Land wrote:
> On Jan 8, 2007, at 3:03 PM, Dave Land wrote:
>
> > Happily, Apple provided a utility that handles it for you:
> >
> >defaults read "${HOME}/.MacOSX/environment"
>
> Actually, making this work in bash (or other shell) requires a little
> more than just reading the file..
On Jan 8, 2007, at 3:03 PM, Dave Land wrote:
Happily, Apple provided a utility that handles it for you:
defaults read "${HOME}/.MacOSX/environment"
Actually, making this work in bash (or other shell) requires a little
more than just reading the file... Here's the relevant chunk from
my
Hello,
On Jan 8, 2007, at 2:31 PM, Brett Calcott wrote:
This does seem to be the case. No amount of fiddling with .profile
.bashrc .bash_profile /etc/bashrc or whatever makes any difference to
the environment that ends up in the GUI version that is started from
the dock.
I don't know if the M
This does seem to be the case. No amount of fiddling with .profile
.bashrc .bash_profile /etc/bashrc or whatever makes any difference to
the environment that ends up in the GUI version that is started from
the dock.
For the moment I just do something like this:
if has("gui_running")
let $PATH=$P
On pon sty 8 2007, vim@vim.org wrote:
> I thought the same thing. But it does not appear to source my
> .bash_profile or .bashrc.
>
> Anyone out there got some clues...?
/etc/profile
/etc/bashrc
?
This will be global for all users (if working :)).
m.
Am 08.01.2007 um 13:26 schrieb striker:
I believe both versions of Vim get its initial info from ~/.bashrc.
Well, actually they get the environment from the shell that starts Vim.
When you start Vim from the bash, it will inherit the environment.
When you start Vim from the Finder (or the Do
On Mon, 8 Jan 2007, Brett Calcott apparently wrote:
> I have just got a Macbook (switching from windows) and
> have downloaded and compiled the latest version of Vim on
> it. It all works fine, but I have a few questions.
Would you mind outlining the steps you took for someone who
is making t
I believe both versions of Vim get its initial info from ~/.bashrc.
In my ~/.vimrc I have the following entry:
" make sure Vim uses the bash shell
set shell=bash
Which verion(s) are you using? I have OS X 10.4.8 and the command
line version of Vim is 6.3.82.
The GUI version is 7.0. Other tha
Brett Calcott wrote:
>
If you type "echo $SHELL" (without the quotes) at the Terminal app
command-line, what is the answer?
/bin/bash for both gui and command line versions.
Brett
Hm, then let's wait and see what the Mac guys have to say.
Best regards,
Tony.
>
If you type "echo $SHELL" (without the quotes) at the Terminal app
command-line, what is the answer?
/bin/bash for both gui and command line versions.
Brett
Brett Calcott wrote:
>
> 1. How do I distinguish between the command line and gui versions.
> Both appear to respond 'True' to has("gui"). Is there another feature
> that I should be looking for.
Many non-Windows versions of GUI-enabled Vim can also run in console
mode.
"classical" way for a sc
>
> 1. How do I distinguish between the command line and gui versions.
> Both appear to respond 'True' to has("gui"). Is there another feature
> that I should be looking for.
Many non-Windows versions of GUI-enabled Vim can also run in console mode.
"classical" way for a script to determine wheth
Brett Calcott wrote:
Hi all,
I have just got a Macbook (switching from windows) and have downloaded
and compiled the latest version of Vim on it. It all works fine, but I
have a few questions.
1. How do I distinguish between the command line and gui versions.
Both appear to respond 'True' to ha
29 matches
Mail list logo
