This is an old bug that seems to never have been addressed (and the original post is not closed):
It is still an issue and still very annoying.
The issue also happens with certain websites (e.g. the job board on LinkedIn), not just macOS apps.
This is an old bug that seems to never have been addressed (and the original post is not closed):
It is still an issue and still very annoying.
The issue also happens with certain websites (e.g. the job board on LinkedIn), not just macOS apps.
Did you read the reply from Licat, one of the developers? It explains it.
If you âPaste without formattingâ (Cmd-Option-Shift-V) does it not strip these characters for you?
I think it was closed because this is expected and/or there is nothing that Obsidian can do about it, without making potentially destructive choices about what is wanted or unwanted.
I did, but I donât see that as a solution since pasting without formatting removes the formatting that is supposed to be there.
I also wouldnât call it expected behaviour since the user does not expect extra visual formatting to magically appear when copy and pasting.
As for the âwithout making destructive choicesâ I agree, but a solution to this could simple be toggled in the settings.
Same trouble, Obsidian+plugins up to date.
âPaste as plain textâ doesnât work just in Obsidian,
âPaste as plain textâ in MS Word, n++, notepad works fine.
Iâve been working in IT for almost 30 years, but I donât remember anything like that when I put âpaste as plain textâ to get something other than just âplain textâ.
I think there is a high probability that the problem is caused by Obsidian itself or one of its plugins. I use, several plugins to manipulate URLs. Since no one here on the forum could advise me, I tried something myselfâŚ
From the list of installed plugins I chose the first one that is designed to work with URL/URI - âAdvanced URIâ.
a) I have verified repeatedly that Obidian is unable to correctly perform âpaste as plain textâ.
b) I made disable this plugin, repeated âpaste as plain textâ - and pasted ⌠plain text !!!
c) I enabled this plugin, repeated âpaste as plain textâ - and pasted again ⌠plain text
Perhaps this could be a workaround in my case of need.
So I dare to say that there is a problem/error under the hood of Obsidian.
So youâre saying disabling a community plugin solved the problem on your end? This is why bug reports are typically not accepted unless the poster has disabled all community plugins or tested in the Sandbox vault.
Itâs not possible to offer support for all the possible combinations of 3rd party plugins.
If you can demonstrate the problem with examples or screenshots, that would be helpful.
It sounds like youâre describing something different than that original bug report. When they used âpaste without formattingâ, it worked. They expected that regular pasting would also automatically strip extra characters. (From my understanding.)
You seem to be saying youâre seeing extra characters even when pasting without formatting. But you havenât showed us what, or how. Where are you pasting from? What are the results? What is your âShow debug infoâ?
The bug was correctly closed because it was determined that the extra characters/paragraphs were there to begin with. To be precise they were in the HTML present in the clipboard that Obsidian uses to make the conversion. In this case, you need to file the bug report to the app that is generating the html in the clipboard not Obsidian.
If this problem happens and there are no extra spaces/paragraph in the html, open a new bug report and attach a copy of the html content present in the clipboard and the result in Obsidian.
Thank you for your quick response. I apologize that my post is incomplete.
I just wanted to let other know that there is at least a workaround for a certain problem.
Workaround helped me, but only for about an hour, then the problem manifested itself again.
Iâll try to disable another plugin(s), or leave it disable for a longer time. Then Iâll compile my findings and submit here, or forward to the plugin author if it turns out that the plugin is to blame.
I will also add debug info