You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1What about a separate GitHub branch where you commit the files in whatever state they are?Arseni Mourzenko– Arseni Mourzenko2019-09-21 22:14:19 +00:00Commented Sep 21, 2019 at 22:14
-
Can't tell if your issue is that you have to recreate the session you left or that you keep forgetting to save your code before walking away. If you developed it all on a shared folder would it fix your problem?candied_orange– candied_orange2019-09-21 22:26:10 +00:00Commented Sep 21, 2019 at 22:26
-
1Just curious: do you have equivalent development tools and environments on Windows and Linux, so you could simply check in the files to a git server (or GitHub) on one system, check them out on the other and continue your work immediately?Doc Brown– Doc Brown2019-09-21 22:32:55 +00:00Commented Sep 21, 2019 at 22:32
-
1Why do you need to switch between multiple machines multiple times throughout the day? Can't you just set one machine as your development environment and the other setup only as a testing environment? Would using KVM switch so you can share one keyboard and mouse for two machines be suitable?Lie Ryan– Lie Ryan2019-09-21 23:22:22 +00:00Commented Sep 21, 2019 at 23:22
-
1What build system do you use? How about a SMB share or NFS share? Also, what is the typical scale of code changes (e.g. couples of lines, or hundreds of lines) you make for each time you switch between the two OSes?rwong– rwong2019-09-22 06:06:35 +00:00Commented Sep 22, 2019 at 6:06
|
Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you