York Zhao wrote:
> I'm switching to Magit 2.1, but I can't find `magit-interactive-rebase' any
> more. Since I'm an extremely heavy user of this function, I really hope it
> hasn't been and will not be dropped.
It's now magit-rebase-interactive, which is in the rebase popup.
--
Kyle
--
You rec
Hello,
York Zhao wrote:
> Hi,
>
> Before Magit 2.1, I can revert a file by selecting the file in
> magit-status-mode
> and hit `v'. However, in Magit 2.1, `v' has been bound to `magit-reverse'
> which
> always gives me the error: "user-error: Cannot reverse unstaged changes". How
> do
> I reve
York Zhao wrote:
> I noticed that numerous functions have changed their name making it
> really hard to figure out the new names, do you know if there is
> somewhere documenting all the function name changes?
I don't think there is, but a good way to approach it is to look in the
relevant popup (
Daniel Dehennin wrote:
[...]
> My problem is that I can not find a quick way to open the files from
> magit-rev buffer or after viewing a file with magit-diff-visit-file.
>
> Is there a way to make “C-u magit-diff-visit-file” open the file at
> current HEAD?
Just to be clear: from the buffer visi
Yuri D'Elia wrote:
> I like to manually expand tabs in magit-diff (on whenever I'm looking
> at diff output).
[...]
> I don't think there would be any side-effect, since there's no point
> in editing the diff itself, except when you're searching in the diff
> for literal tabs.
magit-apply and mag
Yuri D'Elia wrote:
> On 18/07/15 11:38, Yuri D'Elia wrote:
[...]
>> Humm, maybe I could use an overlay to fix just the display then.
[...]
> Do you still think that this could break magit-apply?
No, I think the patch will be applied correctly in that case.
--
Kyle
--
You received this message
Robin Green writes:
> On Friday, 17 July 2015 20:33:09 UTC+1, Kyle Meyer wrote:
>> Daniel Dehennin wrote:
>> [...]
>> > My problem is that I can not find a quick way to open the files from
>> > magit-rev buffer or after viewing a file with magit-diff-visit-
Markus Lachinger writes:
[...]
> So my ideal workflow would be:
>
> magit-diff the branches
>
> --
> | foo.rb|
> | bar.txt |
> | .|
> --
> When I now go onto foo.rb and trigger the functio
Markus Lachinger writes:
[...]
> The motivation / use case is to be able to quickly assess the changes
> that were made i.e. between two branches while having more context
> than just the diff ± a few lines, or just be able to jump around in
> the file.
>
> I could use RET to jump to the file an
Hi Ning,
Ning Shi writes:
> I've noticed that the performance of magit has been noticeably worse
> than before after I upgraded from v1.x to v2.x. I googled around and
> didn't find a solution that solved the problem.
>
> I ran the profiler and collected some results on a simple status
> buffer
Julien Cubizolles writes:
> I'm not sure I'm using the origin/upstream concepts how they should be
> used. I've forked a github repository to add some custom changes, set
> origin (at first push) to the fork in my personal github repo and set
> upstream (through b u) to the repo I forked (zenoroc
Julien Cubizolles writes:
> Kyle Meyer writes:
>> If you don't find the information useful, you can remove
>> magit-insert-unpushed-to-upstream from magit-status-sections-hook.
>
> That will come handy. Considering the frequency of my micro-commits, this
> list o
Hello,
Seb writes:
> Hello,
>
> Using the current magit packages from Melpa, doing magit-clone on a
> github project I get a "Not inside a Git repository" error message on
> *Messages* on the minibuffer after answering "yes" to the question "Set
> `remote.pushDefault' to origin?". However, c
Tim Visher writes:
> A very useful feature of using git from the command line is that when you
> pull from remotes you get a nice summary of everything that's changed since
> you last pulled.
>
> In Magit I just get a confirmation that it was successful.
>
> I know that I can open up the process
writes:
> When trying to quit Magit with typing q, I get:
>
> Debugger entered--Lisp error: (wrong-number-of-arguments (1 . 1) 0)
> magit-mode-quit-window()
> magit-quit-session()
> funcall-interactively(magit-quit-session)
> call-interactively(magit-quit-session nil nil)
> command-exec
Nathaniel Mishkin writes:
> First (and as you've probably surmised), I'm doing all this in a repo with
> a lot of files in it.
>
> Scenario:
>
> * I modify one tracked file and add one untracked file. "git status" shows
> the expected output (info about both the change and the untracked file).
I
Erik van Zwol writes:
> I'm new to magit. I'm in the status buffer, and I only see changes
> made to files in the directory of the file from which I got to the
> status buffer. I am two directory levels down into my project, how do
> I see changes to a file such as .gitignore, which is in the g
[I accidentally dropped the list in the reply. Resending.]
Martin Geisler writes:
[...]
> The only times were I have to drop back to a terminal and raw Git
> commands is when I have merge conflicts. I then run "git mergetool" in
> my terminal to have KDiff3 start on the files in question.
>
>
Noam Postavsky writes:
[...]
> There's no special support in Magit for external tools (Real Emacsers
> use ediff ;) ).
No, smerge is all you need :)
--
Kyle
--
You received this message because you are subscribed to the Google Groups
"magit" group.
To unsubscribe from this group and stop re
Hello,
Martin Geisler writes:
> Hi all,
>
> Does Magit have an option to sort branch names by the order they have
> been used?
No, not that I'm aware of.
>
> I'm using magit-ido-completing-read and as far as I can tell, the
> order of the branches is alphabetically. That is normally not such a
Allen Li writes:
> Is there a way to create a spinoff branch containing one commit?
Hmm, I don't think there is.
> I'm aware that you can use the region to select a number of commits
> for the spinoff branch, but I haven't found a way to select just one
> commit (HEAD). I often make a single c
Allen Li writes:
> On Thu, Jan 5, 2017 at 8:26 AM, Kyle Meyer wrote:
>> I'll open an issue or PR within the next couple days to discuss this.
>
> Thanks!
Looks like Jonas opened an issue for this earlier today.
https://github.com/magit/magit/issues/2920
--
Kyle
-
Lele Gaifax writes:
> Hi,
>
> I seem to remember a way to specify a different Author for a specific commit,
> but I wasn't able to find it in current version of magit/git-commit, just the
> pseudo-headers ala "Suggested-by".
>
> Am I missing something or was the feature dropped?
You can override
Sam Cramer writes:
> Is there a way to have magit prompt for local branches only when
> asking for a branch?
No, not if a command calls magit-list-branches rather than
magit-list-local-branches to generate the collection.
> Alternately, is there a way to have the completions sorted so that
> lo
Kyle Meyer writes:
> Sam Cramer writes:
[...]
>> Alternately, is there a way to have the completions sorted so that
>> local branches appear first?
>
> Not at the moment. There's an issue about sorting branches by commit
> date [*1*] and an issue about positio
John Kitchin writes:
> Has the documentation for writing extensions to magit been moved? All
> I could find is labeled: Magit User Manual (1.2 OBSOLETE): Activating
> extensions.
I'm not sure what documentation may have existed in the past, but I'm
not aware of any documentation for recent versi
John Kitchin writes:
> I have figured out most of it by looking at other extensions, but there
> have been a few points that still aren't clear, mostly related to
> keymaps, menu items, etc.. that I thought there might be some
> documentation somewhere on.
Some information on sections and their
vfclists writes:
> I am using `ediff` to get side by side diffs with `magit` and there
> seems to be no way to move to the next pair of files, after diffing
> the current file.
[...]
> Does the ediff have a method of doing that?
No, not that I'm aware of.
--
Kyle
--
You received this messa
Martin Geisler writes:
>
> I notice that Magit highlights parts in brackets when showing commit
> messages. I typically use that for issue numbers, such as [FOO-123]. Would
> it be possible to have that be a link to the actual issue tracker?
> Something so that I can press RET when point is in the
Paul Smith writes:
> Fairly often I find myself wanting to split commits when I do
> interactive rebasing and I'm wondering if anyone has hints for how to
> handle this more easily using Magit.
>
> What I do today is invoke interactive rebase from Magit and mark the
> commit I want to split with
Hello,
noam.le...@elastifile.com writes:
> Hi, I just updated my magit to latest using emacs packaging(Not sure which
> version was running before).
>
> There's now a big delay after I hit '-i' for interactive rebase. Is this a
> known issue?
I'm not aware of any other reports about this.
--
Silfheed writes:
> Hello
>
> I'm trying to search the logs in the magit-log buffer for all
> occurrences of a particular author. Once I enter into the logs for a
> repo from the status buffer (using ll) how do I search through the log
> buffer by author? Just using regular isearch doesn't seem to
Hi John,
John Shahid writes:
> Hi all,
>
> Is there a way to customize the command that magit run when I commit,
> e.g. using `git ci' (a user defined alias) instead of `git commit' ? I
> used to have a popup action to run `git ci' bound to "i". With the
> recent switch to transient my customi
Lele Gaifax writes:
> Hi all,
>
> when I visit the commit history of a file with magit-log-buffer-file, and then
> enter into a particular commit, I end in a magit-revision buffer showing just
> the details of that particular file, with a title like "Commit FOO limited to
> file BAR".
>
> I tried
jmcki...@gmail.com writes:
> I read the manual about the two branches,
Do you mean two remotes?
> and while it makes perfect sense, it is really useful for my feature
> branch to point to the remote version of itself as the upstream
> branch. This lets me see if anyone else has pushed commits th
35 matches
Mail list logo
