You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/shared/lang/english/markdown/faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Read this if you're still having trouble with configuration. For most examples t
14
14
15
15
## So, how do I setup user's glob?
16
16
17
-
First, let's analyze **File1**. Its full path is `C:/ROMs/Kingdom Hearts/game.iso`. Since our **ROMs directory** is `C:/ROMs`, we can just remove it **File1**'s path.
17
+
First, let's analyze **File1**. Its full path is `C:/ROMs/Kingdom Hearts/game.iso`. Since our **ROMs directory** is `C:/ROMs`, we can just remove it from **File1**'s path.
18
18
19
19
We end up with `Kingdom Hearts/game.iso`. It obvious for us that `Kingdom Hearts` is the title, however parser is dumber than you -- you must specify path portion which contains the title by replacing `Kingdom Hearts` with `${title}`.
20
20
@@ -97,7 +97,7 @@ and only files with `nes` and `NES` will be matched. If you're feeling fancy or
97
97
{*,*/*}/*/${title}.@([nN][eE][sS])
98
98
```
99
99
100
-
Now parser is can match any combination and is effectively case-insensitive. Technically, the following glob will work too, but the one above looks better.
100
+
Now parser can match any combination and is effectively case-insensitive. Technically, the following glob will work too, but the one above looks better.
0 commit comments