LuaTeX-0.80.0  Suppose in current directory we have a simple text file, called text (without extension). The following code gives error in LuaTeX, but works fine in TeX. Why? Is there a simple workaround to make this work?  \newread\infile \openin\infile=text \ifeof\infile \message{I am not able to open the file for reading} \fi \closein\infile \bye   The answer should remark specifically which design decisions in LuaTeX justifies this odd behavior. Is this just a bug which has not been fixed or it is intentional?  Besides, are there any reasons why luatex must append .tex extension in opening file for writing? Why always force an extension if files can quite reasonably be used without it?
120516
I'm having troubles with LuaLaTeX and the listings package: the former doesn't seem to accept me performing \lstinputlisting on a filename that doesn't have an extension.  Minimal example:  Makefile:  hello: hello.c     cc -o hello hello.c   test.tex:  \documentclass[a4paper]{article} \usepackage{listings} \begin{document} \lstinputlisting{Makefile} \end{document}   pdfLaTeX is successful, LuaLaTeX displays the following error:  ! Package Listings Error: File `Makefile(.tex)' not found.  Type X to quit or &lt;RETURN&gt; to proceed, or enter new name. (Default extension: tex)  Enter file name:   I'm using the freshest versions from TeXLive 2012 (pdfTeX 3.1415926-2.4-1.40.13, LuaTeX beta-0.70.2-2012052410).  What's the trouble?
106453
I am supposed to use ls to find files that end in a certain letter, but it does not matter if the file has an extension or not.  For example, I want it to do this  &gt; ls test test.txt test.ascii other.txt  &gt; ls [something] test test.txt test.ascii  So that I can find files that end with a 't', but it doesn't include the file where the extension ends in t  Edit: I am supposed to assume that the only period characters in the filename will be for the extension and there will be no others
99815
I would like to embed a text file in an assembly so that I can load the text without having to read it from disk, and so that everything I need is contained within the exe. (So that it's more portable)  Is there a way to do this?  I assume something with the resource files?  And if you can, how do you do it and how do you programaticaly load the text into a string?
69164
I am trying to create the FMT file by using the latex.ltx for the following procedures.   Copy latex.ltx file from the base directory to my local working directory. Rename this file. I Load my orginal source files for the following commands before the \dump command.  \input xmltex.tex \input Sample.cfg \input Sample.xmt \LoadClass{article} \dump \endinput   I am compailing the ltx file for the following command like latex -ini filename.ltx  First i am getting the following error.  ! LaTeX requires e-TeX. l.98     {LaTeX requires e-TeX}  ?   So i comment the those lines from the ltx file and try to run the ltx file.  %   \errmessage %     {LaTeX requires e-TeX} %   \expandafter\endinput   After comment those lines from the ltx file, i will run the ltx file once again. But i am getting the below mentioned errors.   So, i will change my compilation command etex -ini filename.ltx. But the same errors are repeated.   The .ltx show the plenty of errors during the compilation process  \utfthreeuniglyph ... \expandafter {\the \numexpr                                                   4096*(#1-224)+64*(  ! Extra \else. \unicodechar ...nichar@\number #1\endcsname \else                                                   \errmessage {Unicode   I am unable to fix this error. I place my MWE for your reference.  %%Sample.tex%% \def\xmlfile{sample.xml} \input xmltex  %%Sample.xml &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;!DOCTYPE article SYSTEM "JATS-journalpublishing1.dtd"&gt; &lt;article&gt; &lt;front&gt; &lt;article-meta&gt; &lt;title-group&gt; &lt;article-title&gt;The sample title&lt;/article-title&gt; &lt;/title-group&gt; &lt;/article-meta&gt; &lt;/front&gt; &lt;body&gt; &lt;sec id="j_nanoph-2018-0214_s_001"&gt; &lt;title&gt;Introduction&lt;/title&gt; &lt;p&gt;The &lt;bold&gt;Sample.cfg, Sample.xmt, Sample-entity.sty&lt;/bold&gt; files needs to be converted into unreadable format &amp;#x00C1; &amp;#x00E1;.&lt;/p&gt; &lt;/body&gt; &lt;/article&gt;  %%Sample.xmt%%  \XMLentity{TeX}{\TeX} \XMLentity{LaTeX}{\LaTeX}  %%%%Main Root Tag%%%% \XMLelement{article}%     {}%     {\documentclass{article}%     \begin{document}}%     {\end{document}}% %%%%  \XMLelement{bold}{}{\xmlgrab}{\textbf{#1}}   %%%%Front Matter Tags%%%% \XMLelement{front}{}{}{%   \date{}   \maketitle% }% %%%%  \XMLelement{article-title}{}{\xmlgrab}{\title{#1}}  \XMLelement{title}{}{\xmlgrab}{\section*{#1}}  \XMLelement{p}{}{}{\par}%   Could you please advice how to clear those errors and getting the successful FMT creation for the following source files.
96358
I run the following MWE using LuaLaTeX in TeXworks  \documentclass[11pt,twoside,a4paper]{article} \usepackage{MinionPro}  \begin{document}     \textsc{Hello World.} \end{document}    and it gives an error      File MinionPro.sty not found.  If I now input the file name with the full path,       C:/texlive/2017/texmf-dist/tex/latex/MinionPro/MinionPro.sty   it finds the file, but produces an output that isn't in small caps so there seems to be a substitution at work.  The log file says      Try loading font information for TU+MinionPro-OsF" and "No file TUMinionPro-OsF.fd    which is correct - there are OT1, OT2 fds (among others) but no TU file.  So where should the .sty (and Fd) files be put so that TeXworks will find them?  And will the TU issue then resolve itself?
74917
[Please correct me if my statements are wrong]  TL;DR: pdftex, xetex and luatex exhibit different behaviour. What are these differences and why are they present.    I know of three engines, which implement TeX and support native PDF output: pdftex, xetex and luatex. Unfortunately they are not completely compatible.  pdftex is an ɛ-TeX engine, which is downward compatible to Knuth-TeX, i.e. there will be not difference in the typeset output of pdftex and tex (breakpoints, pagebreaks, ligatures, dimensions, etc. are exactly the same).  Example of an Incompatibility  This is not true for xetex and luatex. I just know of one obvious incompatibility which I will support by a MWE in a moment. To prevent a ligature, Knuth suggest several alternatives in the TeXbook in exercise 5.1     {shelf}ful or shelf{}ful, etc.; or even shelf\/ful, which yields a shelfful (w/ ligature) instead of a shelfful (w/o ligature). In fact, the latter idea—to insert an italic correction—is preferable because TeX will reinsert the ff ligature by itself after hyphenating shelf{}ful. (Appendix H points out that ligatures are put into a hyphenated word that contains no “explicit kerns,” and an italic correction is an explicit kern.) But the italic correction may be too much (especially in an italic font); shelf{\kern0pt}ful is often best.   Thus having the following plainTeX document should always result in the ff ligature being disabled  shelf{}ful \bye   pdftex  The output of tex and pdftex is as expected    luatex  But for luatex I obtain    xetex  For xetex I get the same as for pdftex    but as soon as I load an OpenType font as in  \font\test="CMU Serif" \test shelf{}ful \bye   the ligature reappears    Another example (which turned out to be a bug)  The code  ${}\limits$ \bye   will typeset without any complaint under luatex whereas it will throw the error  ! Limit controls must follow a math operator.   with pdftex or xetex.  This example will also throw the appropriate error for luatexversions > beta-0.79.1.  Summary  In the end my question boils down to several points:   What are the incompatibilities of xetex and luatex with pdftex? Why did the designers choose to break compatibility with Knuth? Can I restore compatibility by making specific design choices (i.e. breaking ligatures with \kern0pt instead of {})?     N.B.: Please don't get too caught up by the example. I'm not asking for a solution to this specific problem. If you are searching for a solution to it, visit those links         List of known incompatibilities  Here I collect links to questions/answers which point out some of the incompatibilities.  It is intended for users contemplating to switch engines, but want to known what to watch out for.
94237
I was trying to find how to pass some text to a file without overwriting what's there already using the > command and I realised I don't know what it's called. Searching for right arrow or right chevron or more than command didn't show up anything. I've always just called it pass to.
92593
If I want to create a new file extension for a binary/text data file that will open on my own application (extension ".mylongfileextensionname" for example), will Windows list it with my aplication (considering that I already listed it on Windows Registry before)?  There is a length limit, I mean, on my example should I use ".mylong" or any specific layout?
7661
Have anyone an idea how i can use \IfFileExist{}{}{} for file names with spaces?  f.e. didn't work  \newcommand{\runI}{D:/Test/run1 - T2} \newcommand\IG[2][]{\IfFileExists{#2}{\includegraphics[#1]{#2}}{\fbox{File #2 doesn't exist}}}  \begin{figure}[htbp] \centering \IG[trim = 40mm 10mm 40mm 2mm,clip = true, width=0.4\textwidth]{\runI/LatexTestFig2.png} \caption{run 1} \label{overflow} \end{figure}   f.e. work  \newcommand{\runII}{D:/Test/run1-T2-Kopie} \newcommand\IG[2][]{\IfFileExists{#2}{\includegraphics[#1]{#2}}{\fbox{File #2 doesn't exist}}}  \begin{figure}[htbp] \centering \IG[trim = 40mm 10mm 40mm 2mm,clip = true, width=0.4\textwidth]{\runII/LatexTestFig2.png} \caption{run 1} \label{overflow} \end{figure}   what can I do? THX
38469
As of version 2.7 of luaotfload the support for font feature files (.fea) .  On the  Hans showed how to make font substitution work through Lua.  More examples are available in the latest ConTeXt distribution (, , , , , , )  In the past I have been using font feature files to adjust the kerning of fonts on-the-fly.  From Hans' example it is not clear to me how to adjust kerning in the new syntax.  The below example does not work as intended.  \documentclass{article} \usepackage{fontspec} \directlua{ fonts.handlers.otf.addfeature {     name = "kern",     {         type = "pair",         data = {             [0x0041] = { [0x0056] = { false, { -200, 0, 0, 0 } } },         }     } } } \setmainfont{Latin Modern Roman} \begin{document} AV \end{document}   Can we have a comprehensive guide on how to adjust font features with LuaTeX with the fonts.handlers technique?    Related questions:  (These involve hooking into the luaotfload.patch_font callback)
95760
Just noticed it works on Maverick.. the colon character : is valid for file and directory names (I accidentally entered it for a filename in Atom).  Can't find any reference to it becoming valid though ( still marks it as invalid).  It works in the Atom editor.  I can create a file called : with nano.  This works echo 'test' &gt; : &amp;&amp; cat :  In TextWrangler it only works if the file already exists but won't create it (with command line tools installed edit :)  Is this new from Mavericks? Works in Yosemite? Before?  Edit: A few more tests:    TextEdit won't allow me to enter it and always replace it with - Finder won't allow me to create a folder with the name :  A : file created via command line is displayed as / in Finder.. and double clicking it will open it in TextEdit. TextEdit will load its content but show the name / in the title bar.
100326
Call me crazy, but I'm sure I remember this capability existing in previous versions of Windows.  In Windows 7, we can have file extensions Off... or On.  Pick one.  Is there some obscure switch buried in the registry to have Explorer show specific extensions, but leave the rest hidden?  In my case, I'd like to always show extensions for text files (*.txt, *.csv, *.tdt), because I frequently have to handle flat files which may come in with a .txt extension where I need it to be .csv, for example.  I'd rather not have extensions on all the time, it's just clutter for almost all files.
27909
I was trying to concatenate text files in sub-folders and tried:  cat ./{mainfolder1,mainfolder2,mainfolder3}/{subfolder1}/book.txt &gt; out$var   However this did not return anything. So, tried adding a non existing 'subfolder2'  cat ./{mainfolder1,mainfolder2,mainfolder3}/{subfolder1,subfolder2}/book.txt &gt; out$var   And this time it did work out, concatenating the files successfully. Why does this happens?
37790
As the question goes, how does Ubuntu know what file type a file without extension is?  When I save a file as "Untitled Document" without any extension, how does it know? Same thing for video and music formats...
102481
Hi I want to prepend text to a file.  For example I want to add tasks to the beginning of a todo.txt file.  I am aware of echo 'task goes here' &gt;&gt; todo.txt but that adds the line to the end of the file (not what I want).
60846
I have a directory full of text files. My goal is to append text to the beginning and end of all of them. The text that goes at the beginning and end is the same for each file.  Based on code I got from the web, this is the code for appending to the beginning of the file:  echo -e 'var language = {\n$(cat $BASEDIR/Translations/Javascript/*.txt)' &gt; $BASEDIR/Translations/Javascript/*.txt   This is the code for appending to the end of the file. The goal is to add the text }; at the end of each file:  echo "};" &gt;&gt; $BASEDIR/Translations/Javascript/*.txt   The examples I drew from were for acting on individual files. I thought I'd try acting on multiple files using the wildcard, *.txt.  I might be making other mistakes as well. In any case, how do I append text to the beginning and end of multiple files?
91917
Is it possible to set a default application to open files with no extension?  I'm not referring to files with hidden extensions, but those completely lacking an extension -- e.g. README, CHANGELOG, mbox, etc.  "Open With" => "Change All" on these files doesn't work, returning the error shown below:    Ideally, I would like the system to try opening all such files in TextMate.  I know I can drag files onto Dock icons to open them in specific apps, but I'm looking for a more seamless solution than that (especially since I have my Dock auto-hide, which makes it much more cumbersome).  I am familiar with the  QuickLook plugin that can enable QuickLook for some of these files, but I would prefer a solution with selecting/copying/editing capabilities.