Comments (9)
I don't think I am familiar with this. I will need to look into it since this is the first I have heard of this being a thing.
from obsidian-linter.
I've not used BRAT before but I'm guessing it's easy enough. Any reason why its better than being provided a zip of the file? I'm willing to help nonetheless.
BRAT is simpler as I can create a release and get more eyes on it than having to create a zip for a single issue. Though for smaller things with faster responses, a zip makes more sense when less people are to be involved.
this affects several different rules and may not be easy to gauge what all has been affected.
Shouldn't your tests catch these things? Just assuming here.
It would be great if tests caught these things. But as a dev I have a very different view on how to use rules together and what rules actually get used. It seems more often than not, when the complexity increases, the scenarios I think are relavent do not cover what users will try.
from obsidian-linter.
I went ahead and merged the PR for these changes. I plan to make a release later this week, but we will see if that pans out.
Please let us know if there is an issue with this on master or in the next release.
from obsidian-linter.
Also, @redactedscribe , is this essentially an add-on to #933 or is there something that makes this different than adding an option for what line break value to use? This will help me better understand what to do moving forward.
from obsidian-linter.
I don't think I am familiar with this. I will need to look into it since this is the first I have heard of this being a thing.
I was surprised I couldn't find a pre-existing issue.
Also, @redactedscribe , is this essentially an add-on to #933 or is there something that makes this different than adding an option for what line break value to use? This will help me better understand what to do moving forward.
It looks like it's essentially the same thing but without mention of \
.
Just to state it in my own words: I'd like Linter to treat \
identically to
(double space) line endings. I didn't initially think to ask for an option to make line breaks consistent but it makes sense. So, be able to choose the preferred line break
, <br>
, <br/>
, or \
(if you deem backslashes are valid too).
from obsidian-linter.
I don't think I am familiar with this. I will need to look into it since this is the first I have heard of this being a thing.
I was surprised I couldn't find a pre-existing issue.
Also, @redactedscribe , is this essentially an add-on to #933 or is there something that makes this different than adding an option for what line break value to use? This will help me better understand what to do moving forward.
It looks like it's essentially the same thing but without mention of
\
.Just to state it in my own words: I'd like Linter to treat
\
identically to(double space) line endings. I didn't initially think to ask for an option to make line breaks consistent but it makes sense. So, be able to choose the preferred line break
,
<br>
,<br/>
, or\
(if you deem backslashes are valid too).
To clarify, are you saying that you would expect the two trailing spaces to replace values like
, <br>
, and <br/>
with \
if there was an option to set the line ending indicator? I ask because that is possible, but may change how things would be implemented.
from obsidian-linter.
To clarify, are you saying that you would expect the two trailing spaces to replace values like
,
<br>
, and<br/>
with\
if there was an option to set the line ending indicator? I ask because that is possible, but may change how things would be implemented.
What I expect is that if a line ends with two spaces and I've defined two spaces
as my preferred line break syntax, then any line ending with the any of the alternatives, i.e. a backslash or the BRs, would get converted to double spaces.
If instead backslash \
was my preference, convert all alternatives to \
. If I have no preferred line break syntax set, do not try and make line breaks consistent.
Double spaces, BRs, and backslash would ideally all be supported as valid line break syntax at the end of a line.
from obsidian-linter.
I did start work on this before I got sick and then distracted with other tasks. I will need to see how far in I got on this since this affects several different rules and may not be easy to gauge what all has been affected.
If I were to proceed with this and put out a beta release for this would you be interested in testing it via BRAT @redactedscribe ?
from obsidian-linter.
I've not used BRAT before but I'm guessing it's easy enough. Any reason why its better than being provided a zip of the file? I'm willing to help nonetheless.
this affects several different rules and may not be easy to gauge what all has been affected.
Shouldn't your tests catch these things? Just assuming here.
from obsidian-linter.
Related Issues (20)
- Bug: Remove space header when option `RemoveSpaceAroundCharacters` is enabled and Katakata is beginning of the line HOT 1
- FR: Matching / Tidying Header Pound Signs
- Bug: capitalize-headings, yaml-title, yaml-title-alias require two lint passes to resolve
- FR: Ignore yaml-title rule if key exists with a value
- FR: Enable Linter to Run on Files That Are Not Currently Open in Obsidian HOT 3
- Bug: Tags are not moved into the YAML frontmatter if they have emoji in it HOT 2
- Bug: Ellipsis substitution inserts a range mark HOT 2
- Bug: Some strings are only processed on alternate pastes HOT 6
- Bug: Heading blank lines not only adds a blank line before/after headings, it also removes consecutive blank lines HOT 6
- FR: Multiple linter settings/settings HOT 2
- Bug: First letter in Title Case not Uppercase when preceded with numbers or special characters HOT 5
- FR: Restrict regex to note body HOT 14
- Bug: Duplication. `.. Linter | Spacings | Tabsize` already defined in `Obsidian | Settings | Options | Editor | tab size` HOT 2
- FR: Start Header Increment at Heading Level 2 - Add option to ignore very first heading. HOT 3
- FR: formatting/deleting extra lines in code block HOT 2
- Bug: Linter setting breaks 'Share Note' plugin HOT 3
- FR: `YAML Timestamp` section is wonderful, but it needs to ignore your templates. HOT 3
- Bug: HTML comment treated as paragraph HOT 3
- FR: Lint on file change isn't checking whether the file was actually changed HOT 2
- Bug: YAML modified timestamp / order of operations HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from obsidian-linter.