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

[FR]: Internal links should provide an option to exclude attachments. #380

Closed
1 task done
ForsakenDelusion opened this issue Jan 25, 2025 · 1 comment
Closed
1 task done
Assignees

Comments

@ForsakenDelusion
Copy link

ForsakenDelusion commented Jan 25, 2025

Issue validation

  • I checked the issue to prevent duplicate

Is your feature related to a problem ?

No response

What solution do you want to see ?

When I need to use Dataview, I have to enable the Internal Links option, which unfortunately converts my images to relative paths. The major issue is that this conversion seems to occur after the article content has been processed by regular expression replacements, leading to some of my image links being altered in ways I do not desire. My use case involves publishing with Hugo; once the Internal Links option is checked, my image links transform into something like "../../../../static/imagines" (where static/images is the upload location I set in the attachment options). Even if I use regular expressions to change Obsidian image links to "/images/xxx.png", this feature still modifies my image links. I've attempted to set the Link:false option, but it fails to work when the article contains both Dataview and images.

Describe the alternative you've considered

Manually changing the image directory, but that's just too silly.

OS

MacOS

Anything else?

No response

Plugin version

7.5.3

Obsidian version & debug log

v1.7.7
@Mara-Li
Copy link
Member

Mara-Li commented Jan 25, 2025

for the regex you should set on "after":

Image

I won't add an option to exclude image, as they are a lot of option to modify them with the regex.

@Mara-Li Mara-Li closed this as completed Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants