New issue
Advanced search Search tips

Issue 907511 link

Starred by 1 user
Status: WontFix
Owner:
joelhockey@chromium.org
Closed: Nov 26
Cc:
weifangsun@chromium.org
tbuck...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Weird filename when copying ".emacs" file that already exists

Project Member Reported by tbuckley@google.com, Nov 21 
Chrome Version: 71.0.3578.57
OS Version: 11151.33.0

What steps will reproduce the problem?
1. Create a .emacs file in Linux files
2. Copy it to Drive
3. Copy it back to Linux Files

What is the expected result? User is asked to replace, or file is given a reasonable name like ".emacs (1)"
What happens instead of that? File is named " (1).emacs"

Comment 1 by weifangsun@chromium.org, Nov 26

Labels: M-72
Hmm - This seems intended. If the file name already exists, the (1) suffix should be appended prior to the file type indicator?

Comment 2 by joelhockey@chromium.org, Nov 26

Status: WontFix (was: Assigned)
Yes, I haven't yet looked to see which bit of code does this, but I also believe it is intentional that we add the number prior to the file extension or last period in the filename.

Comment 3 by vapier@chromium.org, Nov 26

Summary: Weird filename when copying ".emacs" file that already exists (was: Weird filename when copying .emacs file)
►

Sign in to add a comment