@MarioS.E. well I just stuck some - in at places that seemed like they might make sense. If one dictionary finds one extra place is OK that's not surprising The width of an i isn't likely to make much difference, breaking either side will stop the line being so under full
@MarioS.E. there is no right and wrong about hyphenation, different dictionaries will give different answers, and (luckily for me) the dictionary quoted agreed with all the hyphenation points I guessed, plus one extra so any breaks due to the code I suggested would be OK according to the dictionary.
@MarioS.E. well yes makes potential break points there but I said bio-medi-cine and webster said bio-med-i-cine so the only difference is whether you allow it to break before the i.
@MarioS.E. if I'd have said bio-me-di-ci-ne then that would have allowed a break before the d which would have been wrong according to the dictionary, but I didn't so all is OK:-)
@PauloCereda Hi Paulo! :) If you get a change, I'd love to know if you have any thoughts on tex.stackexchange.com/questions/107598/… :) or indeed if the problem can be recreated...
@egreg I already noticed. Everything’s fine. But side note: Where I would have to add the dictionary files? In MiKTeX they are directly in <texmf>\hunspell.
@PauloCereda I don't think it is arara- to be honest I wasn't sure that it was to start with, but the fact that the script ran from the command line but not in arara was the only reason...
I think i need to check my modules are in order...
An all-together resource like this specifically for Windows users on MikTeX would be amazing - unless of course there is a duplicate you'd kindly point to.
@PauloCereda same result with the file I posted... If I use this version, it works ok
#!/usr/bin/perl
use strict; use warnings; use FindBin; # help find defaultSettings.yaml use File::Copy; # to copy the original file to backup (if overwrite option set) use File::Basename; # to get the filename and directory path use Getopt::Std; # to get the switches/options/flags #use File::HomeDir; # to get users home directory, regardless of OS #use YAML::Tiny; # interpret defaultSettings.yaml
@egreg Hmm, tried it. I have a portable TL, there is only texlive\texmf-local. I created there texworks\dictionaries, put dictionary files ina nd refreshed file lists, but it does not work. (And I made a mistake, in MiKTeX they are in hunspell\dicts.)
@texenthusiast I'm sorry to be a drag, but I would think the Q in question would most certainly fall under "However, if your motivation is “I would like others to explain ______ to me”, then you are probably OK. " ... While the question doesn't seem to show much effort, it definitely has the air of bewilderment about it. OP is lost.
@SeanAllred tex.sx has already got beautiful Q& A and so for better knowledge database i thought we are duplicating the efforts. Let's see what happens i am not the one to vote to close down. I just put my request. See my comments in Q. BTW your answer is also great :).
Thanks @texenthusiast - that means a lot coming from you. I saw your comments and integrated your efforts into the CW, but I guarantee that the first thing I did was scour TeX.SX for a potential duplicate. While most of the questions on this site are PracticalQuestion->PracticalAnswer, there are quite a few that aren't (Explaining LaTeX to your grandmother, etc.)
In the beginning I use the following code. So far so good.
\documentclass[pstricks,border=12pt]{standalone}
\usepackage{multido}
\usepackage[nomessages]{fp}
\def\LoadConstants{}
\newcommand\const[3][3]{%
\edef\temporary{round(#3}%
\expandafter\FPeval\csname#2\expandafter\endcsname
...
@PauloCereda save still doesn't work for me, is it possible for me to annotate the lua with some print statements so it echos where it thinks it is writing to? I suppose I could read the lua manual but that would be cheating
@PauloCereda Ah save works on the example1.tex in git and makes a file the same apart from eol at end and a comment with the date , but on mine it says
:: I'm sorry, but the tests from the log file and
:: the tests from the source file differ. I cannot
:: proceed. Stopping execution.
I guess the difference is that mine generates a TeX error.
@DavidCarlisle Oh, we are making progress! :) If I remember this message, it's because the .tex file has, say, test1 and test2, and the .log is expected to have the same markups.
@PauloCereda as I mentioned in email I don't much like the weird split between comments and tex markup, in this case % id: e2-1 has to match \begin{TEST}{e2-1}
@PauloCereda I made my test by just hacking the existing one (of course:-) and changed the name in half the places it appeared. If the argument to \begin{TEST}has to match the preceding id comment it would be simpler just to not have it.
@PauloCereda well I would either use comment syntax for both or tex syntax for both, I don't see why the author name and the expected result are comments but the test is a latex environment.
But anyway having got one silly test to work `- Congratulations, none of your tests failed! ` should I check it in and see if I really do have write access?
@PauloCereda yes not complaining, just saying that that split is something I don't "get" at present. especially the expected result being a comment I think will b epainful for bigger tests (the old test suite has several multipage \showoutput logs as expected result
@DavidCarlisle Agreed. Joseph and I planned a special directive with loadfile("foo.tst") used in the % expects: line in order to load the content instead of inline'ing it. :)
@DavidCarlisle I double-checked, you have write permissions. :) Have fun. :)
I am not sure that this is a right fit for SE, but I will risk it.
I was recently acquainting myself with the xy-pic package, and I found the included exercises very helpful in getting up to speed with the package.
It made me think how great it would be to have a set of TikZ exercises that aid...
I've looked through the configuration menus several times, but haven't been able to find a way to change the color of or remove altogether the dashed blue box that appears around a folded code header (while keeping the folding itself). Is it not possible or have I just missed it?
In the beginning I use the following code. So far so good.
\documentclass[pstricks,border=12pt]{standalone}
\usepackage{multido}
\usepackage[nomessages]{fp}
\def\LoadConstants{}
\newcommand\const[3][3]{%
\edef\temporary{round(#3}%
\expandafter\FPeval\csname#2\expandafter\endcsname
...
I am not sure that this is a right fit for SE, but I will risk it.
I was recently acquainting myself with the xy-pic package, and I found the included exercises very helpful in getting up to speed with the package.
It made me think how great it would be to have a set of TikZ exercises that aid...
I've looked through the configuration menus several times, but haven't been able to find a way to change the color of or remove altogether the dashed blue box that appears around a folded code header (while keeping the folding itself). Is it not possible or have I just missed it?
