I am betting that for i * do echo "$i" done would work in that circumstance.īut, as pointed out, if the spaces in the themes really bother you, then just rename them. And in fact, it’s the same solution as you use in Windows: add quotes. 2011) GNU bash 4.2.37(1), the syntax for i in * do echo $i done worked as expected from the command line when it ran across a filename with a space: it printed that spaced filename on one line.īut even if you’re on a shell that doesn’t behave the same as my bashes, and really did split the filename over two lines, there should be a way around the problem. 2004) GNU bash 3.00.15(1), or in my old but more recent (c. Your linux example is in a slightly different syntax than I’m used to which shell is it? On some linux systems I have access to: in an ancient (c. Then again, the same is true on Windows: for example, the wrong C:\Program Files (x86)\Notepad++\notepad++.exe %1 as your “open” file association in the registry, vs the right "C:\Program Files (x86)\Notepad++\notepad++.exe" "%1". You’re right, some scripts / syntax won’t work well on linux when there’s spaces in the name
But the issue is that the embedded blank creates the appearance of three files, in this case, rather than , This is an abbreviated example which does not address all of the issues nor any of the possible solutions. This means that files with an embedded blank need additional support to be processed in a shell.įor example, if we have a directory with lhsrhs and “lhs rhs” then a command such as “for i * do echo $i done” will return “lhsrhs”, “lsh”, “rhs”, yielding three files instead of two. But in Linux, lhs and rhs are each treated as a separate file. For example, if a file has the format “lhs blank rhs” then in Windows, life proceeds well. The embedded blank causes issues for linux based commands.
FYI, the installation directory contains which I assume is the default stylers.xml.Īs to the blank issue… A file whose name is “myfile” is treated ‘well’ in a linux shell. %AppData%\Notepad++\ contains stylers.xml.
0 kommentar(er)
