Re: Fugitive

On 08/07/11 16:10, eleanor wrote:
> Hi, I'm testing the fugitive plugin for the time being and I've come accross
> the following problems:
> 1)
> - If I add and commit a file called a.txt with the text "aaa"
> - and then change the text to "bbb" and save it and commit it
> - and then change the text to "ccc" and save it (without commiting)
> - and then do the Gdiff ... I get to compare the "bbb" against "ccc"
>
> Why? Shouldn't Gdiff only compare values that form the actual revisions - so
> in this case the "aaa" against "bbb", since the "ccc" is not part of a
> revision yet - because it has not been commited to the repository.
>
> 2) How can I pull/push to the remote repository?
>
> 3) Is it possible to add/commit all the files to the repository/working
> directory?
>
> --
> View this message in context: http://vim.1045645.n5.nabble.com/Fugitive-tp4564868p4564868.html
> Sent from the Vim - General mailing list archive at Nabble.com.
>

I don't know fugitive, but from your post I gather that it's some kind
of Vim plugin to control a version control system.

Which VCS is fugitive using? I think I can answer if it's Mercurial, but
if it isn't, then maybe you should ask in some newsgroup, mailing list
or forum dedicated to that particular VCS?

So the following assumes that the underlying VCS is Mercurial:

1) The answer is found by doing "hg help diff":

"when no revisions are specified, the working directory files are
compared to its parent."

Understanding this sentence needs a bit of Mercurial terminology: the
"working directory files" are the actual files in the directory tree
starting at the repository root; "its parent" is the "current" changeset
(the one latest "updated" to). They will differ if and only if you have
uncommitted changes. So "hg diff" with no arguments tells you what your
uncommitted changes are.

2) If you have a clone, you can always pull from the remote repository
(unless the right to pull has been revoked since you made the clone).
The simplest way to do it is "hg pull" (with git, that would be "git
fetch"). Pushing requires write access to the remote repo, and its admin
may or may not be willing to give you that permission. Ask him (or her),
not us. If you aren't allowed to push yourself, then maybe you're
allowed to send patches ("hg diff") to someone who is.

3) Yes it is: see "hg help addremove", "hg help commit".

Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
128. You can access the Net -- via your portable and cellular phone.

--
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