https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #11 from Manu ---
Any update on this? I still find this kind of annoying. I understand the "Save
as" scenario is a moot point (I would still go for "also keep them"), but I
think just saving should keep them (that's what, e.g., Kate does).
https://bugs.kde.org/show_bug.cgi?id=419109
funkybom...@gmail.com changed:
What|Removed |Added
CC||funkybom...@gmail.com
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #10 from Manu ---
(In reply to Stefan Brüns from comment #8)
> (In reply to Manu from comment #6)
> > maybe out of my depth here, but I think that goes against the baloo
> > philosophy: if you do that, then *every* program handling the file
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #9 from tagwer...@innerjoin.org ---
(In reply to Stefan Brüns from comment #7)
> There is no "if ..." here.
The naive view is applications ought to read, copy, save info in the extended
attributes _as_if_ it was embedded in the file. It's a
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #8 from Stefan Brüns ---
(In reply to Manu from comment #6)
> maybe out of my depth here, but I think that goes against the baloo
> philosophy: if you do that, then *every* program handling the file must know
> about those attributes (acroba
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #7 from Stefan Brüns ---
(In reply to tagwerk19 from comment #5)
> What would happen if this information was part of the file (rather than in
> the extended attributes)? It would be copied/saved as part of the file and
> managed within the a
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #6 from Manu ---
maybe out of my depth here, but I think that goes against the baloo philosophy:
if you do that, then *every* program handling the file must know about those
attributes (acrobat reader, e.g., would probably crash); extended a
https://bugs.kde.org/show_bug.cgi?id=419109
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #4 from Nate Graham ---
Good question indeed. Definitely a yes for the save case. For Save As I am
leaning slightly towards preserving as well.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #3 from Manu ---
...that's a good question. I would also do it for "Save as...". When I do
"Save us" I expect I'll get a "exact" copy. Anyway, my use case is only for
"Save", so I'm fine either way :)
Thanks for looking at this, by the
https://bugs.kde.org/show_bug.cgi?id=419109
--- Comment #2 from Stefan Brüns ---
For "Save", I would definitely vote for "preserve as much as possible".
For "Save as ...", I am not sure. There are pros and cons for both
possibilities.
Cons:
- It may lead to information leakage. Tags, comments,
https://bugs.kde.org/show_bug.cgi?id=419109
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org,
|
12 matches
Mail list logo
