Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Case conflicts (Day One) #259

Closed
bitic opened this issue Jul 31, 2014 · 4 comments
Closed

Case conflicts (Day One) #259

bitic opened this issue Jul 31, 2014 · 4 comments
Labels
🔒 Outdated

Comments

@bitic
Copy link

bitic commented Jul 31, 2014

Hi,

Using jrnl 1.8.2 I launched the command: jrnl --edit

and it opened my Day One entries (my only journal) in a big file in Emacs (my editor).

As I didn't want to edit the whole journal, I quit Emacs (C-x C-#).

This duplicated every entry in my journal with a Case Conflicted file.

I'm using
Python 2.7.3 in Debian 3.2.60-1+deb7u1 x86_64

@maebert
Copy link
Contributor

maebert commented Aug 4, 2014

Hi, just to make sure I fully understand what happened - after editing, in your DayOne Folder, you've got twice as many files, for each upper case one a lower case one as well?

@bitic
Copy link
Author

bitic commented Aug 12, 2014

Yes.

El 04/08/14 7.13, Manuel Ebert ha escrit:

Hi, just to make sure I fully understand what happened - after editing,
in your DayOne Folder, you've got twice as many files, for each upper
case one a lower case one as well?


Reply to this email directly or view it on GitHub
https://github.com/maebert/jrnl/issues/259#issuecomment-51018264.

maebert added a commit that referenced this issue Jan 11, 2015
Correct issue #259, also fix issue with specifying DayOne journals in install
@nikvdp
Copy link

nikvdp commented Sep 6, 2015

@maebert This issue was fixed in PR #325, should be safe to close

@maebert maebert closed this as completed Dec 4, 2015
@lock
Copy link

lock bot commented May 21, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the 🔒 Outdated label May 21, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🔒 Outdated
Projects
None yet
Development

No branches or pull requests

3 participants