On Tue, Nov 19, 2013 at 6:20 PM, Matthieu Moy
matthieu@grenoble-inp.fr wrote:
One thing the command-line does well is to give names to concepts
(basically, command names, option names, ...). It's easy to write in a
tutorial or an email run the command 'git foo'. It's less easy to
write
On 19/11/13 06:11, Matthieu Moy wrote:
I was wondering whether others had similar (or not) experience. In
particular, as a teacher, I'm wondering whether I should push my
students towards the GUI in the IDE, or advise them to keep using the
command-line (we teach them git with the command-line
On Mon, 18 Nov 2013 18:42:26 +0100
Philippe Vaucher philippe.vauc...@gmail.com wrote:
[...]
When they understand git reasonably (or if they are not lazy people
and willing to learn), then show them full integrations like
TortoiseGit (or probably the Netbeans plugin), which are nice when
On Monday, November 18, 2013 06:11:54 PM Matthieu Moy wrote:
Hi,
I'm normally an Emacs+command-line user, but I also use Eclipse or
Netbeans on some projects. I tried using EGit and the Netbeans plugin
for Git, but found the GUI both more comlex and less powerful than the
command-line. I
Matthieu Moy matthieu@grenoble-inp.fr writes:
[...]
I was wondering whether others had similar (or not) experience. In
particular, as a teacher, I'm wondering whether I should push my
students towards the GUI in the IDE, or advise them to keep using the
command-line (we teach them git
Thomas Koch tho...@koch.ro writes:
I'm a software engineer now with an education as a high school teacher. From
a
theoretical point of view it's preferable to avoid any abstraction done by a
GUI and use commandline Git. Only gitk is useful to have a visual _feedback_
of the actions done
Thomas Koch tho...@koch.ro writes:
But also from experience I can tell that without exception everybody whom I
teached Git understood it only after being introduced to the basic concepts
of
Git and how to inspect and operate them on the commandline. Others told me
from similar
Junio C Hamano gits...@pobox.com writes:
Perhaps I am being naïve, but I would expect that a GUI is a much
better vehicle to help users build the right mental model.
One thing the command-line does well is to give names to concepts
(basically, command names, option names, ...). It's easy to
Hi,
I'm normally an Emacs+command-line user, but I also use Eclipse or
Netbeans on some projects. I tried using EGit and the Netbeans plugin
for Git, but found the GUI both more comlex and less powerful than the
command-line. I end-up using command-line git in a terminal, outside the
IDE (and do
I'm normally an Emacs+command-line user, but I also use Eclipse or
Netbeans on some projects.
Did you give magit a try? It's really an awesome emacs plugin, which
gives me pretty much the same control as the command line experience
without the pain. Ask me more about if if you're interested.
On Mon, 18 Nov 2013 18:11:54 +, Matthieu Moy wrote:
...
I was wondering whether others had similar (or not) experience.
Similar. When I used eclipse I didn't even try to use the plugins
and just stayed on the command line. (Well, almost, but back then
jgit couldn't deal with submodules which
Philippe Vaucher philippe.vauc...@gmail.com writes:
I'm normally an Emacs+command-line user, but I also use Eclipse or
Netbeans on some projects.
Did you give magit a try?
I've used the Git backend for DVC in the past. I gave Magit a try very
long ago, and found DVC superior at that time (I
12 matches
Mail list logo
