What would a git commit look like when two distinct programmers have inputted characters into the file?
Code together in real time with Teletype for Atom
161–170 of 230 posts
Re: Code together in real time with Teletype for Atom
#162Earlier quoted context omitted.
Defaulting to whatever the document is currently using would be sane?
The document isn't "using" anything, since a document is a passive object. Unless you have something like vim modelines where you configure it at the top of the file like `/* vim: set tabstop=8:softtabstop=8:shiftwidth=8:noexpandtab */ `, the document itself doesn't know anything about how things _should_ be (which is the important part).
an opened document inside an editor is absolutely aware of this, and this is what you're collaborating on. almost all IDEs support EditorConfig, which makes standardizing on things like that across teams trivial.
Re: Code together in real time with Teletype for Atom
#163[A] [T]on [O]f [M]emory
Re: Code together in real time with Teletype for Atom
#164Earlier quoted context omitted.
> As time goes on the resource usage becomes less of a problem. Yet vim is still more popular today by a wide margin. :) It's not just about memory usage; it's about lag. Atom felt laggy to me. I also value my time, and I can't stand waiting for my editor.
It was the lag (and at the time, struggling to open "large" files) that stopped me giving it more than a cursory check a year or so ago. No idea if it's worth looking into again? Would be hard to beat sublimes snappiness doing almost any task.
There's been a massive amount of performance work in the last year. Definitely give it another try :) (disclaimer, on the Atom team)
Re: Code together in real time with Teletype for Atom
#165“participants all keep their own custom key bindings, packages, and themes.” what happens when two different people editing the same document have two different settings for # spaces per tab character? whose takes precedence? (Or would there be a possibility of inconsistent spacing depending on who is adding a tab?)
If it is displayed spaces per tab character, then there is no conflict in the file but the appearance should be different to different viewers.
If it is space characters replacing a tab keypress, then the spaces in the document should reflect the conversion ratio of the user that typed the tab.
Re: Code together in real time with Teletype for Atom
#166I think blockchain will help us with this. You could substantiate who wrote what in an immutable chain. A non-editable git blame!
Re: Code together in real time with Teletype for Atom
#167What would a git commit look like when two distinct programmers have inputted characters into the file?
One common way to attribute multiple authors in a commit is to add a `Co-authored-by` commit message trailer. You can read more about git commit trailers at https://git-scm.com/docs/git-interpret-trailers.
As an example, if this was a commit message, the trailer adding my attribution would be like this:
`Co-authored-by: FirstName LastName `
Re: Code together in real time with Teletype for Atom
#168That's pretty nice, kudos! By the way, I'm impressed no one mentioned tmux' remote session in this thread.
Re: Code together in real time with Teletype for Atom
#169I can appreciate your efforts here. It isn't trivial to put something like this together but I'm going to go ahead and state the obvious: Face to face is far superior to a solution such as this one for what I think are self evident reasons. You're better off, by orders of magnitude, getting on a plane or train and going to see your code buddies. When I'm coding with someone we're not usually on the same files or piec…
yeah, I use tmux, ssh for this. dev session in a container incase the person does something stupid. hangouts for voice/video
Re: Code together in real time with Teletype for Atom
#170I can appreciate your efforts here. It isn't trivial to put something like this together but I'm going to go ahead and state the obvious: Face to face is far superior to a solution such as this one for what I think are self evident reasons. You're better off, by orders of magnitude, getting on a plane or train and going to see your code buddies. When I'm coding with someone we're not usually on the same files or piec…
Being together in person doesn't solve the problem of wanting to edit the same code simultaneously. For some projects, git is enough, but for something really small this seems like it would really help.
dual keyboards & mouse.