@AlanMunn -- I think not. there's a tag "logging" (which I think would be better as "log-file", but ...) with 81 questions, but I didn't spot anything promising. (A comment on one question mentioned texloganalyser.) At BachoTUG 2017, I gave a presentation on debugging LaTeX files and you're most entirely welcome to steal from that. I agree strongly that a good description of using a log file is much needed, and offer to help compile it.
@AlanMunn -- There's also a tag "debugging" with 308 items. One promising question: Teach me to debug. (There seem to be several more. I'm going to add a category "Debugging & log files" to the "often referenced questions" list. But there's no really good general question/answer.)
@PhelypeOleinik -- I just added that to the "Often referenced questions list" on meta. If you find some other good ones, please feel free to add them there.
@DavidCarlisle I see. But any font that works with [pdf]tex should also work with dviluatex, if I got it right. I was just surprised I would need [T1]{fontenc} in a minimal document to be compilable with dvilualatex.
Yay, first time I started Word today, just opening a document and activating editing, and it's going unresponsive :(
FROM OPENING A SIMPLE TWO PAGE DOCUMENT!!!
(sorry for loosing my cool and starting to scream)
The amount of work-time I'm losing because of that stupid program lets me question whether I'll get my PhD eventually. And that's just half a week into my PhD...
@JosephWright you mean it should've crashed 5 times already?
@JosephWright I had the great idea to create a Word file in which I document each and every crash. While doing so it crashed. So we're at 3 crashes today!
2
Something is terribly wrong here. My Word is pretty much in factory settings. I only made two changes in order to keep it bug free: I switched to the dark grey theme instead of the ugly blue, and I inverted the colours in reading mode to get black paper with white colour.
Seems like in Word, light doesn't attract bugs.
AND IT CRASHED THE FOURTH TIME! Again while starting that ingenious project of documenting crashes in Word.
@Skillmonlikestopanswers.xyz -- Sounds like you're doomed. I hope these crashes don't affect anything else, like your ability to report them here. (Nothing we can do to keep them from affecting your sanity, for which we can only commiserate.)
Next Word crash! I created a new file. Wrote the sentence "This is some serious text." and switched to reading mode. In reading mode I inverted the page colour to ease my eyes and work safely (remember, light attracts bugs). When I switched to FF and back to Word it crashed.
@JosephWright I wanted to edit my word_crashes document. Then there was your answer, so I switched to FF to answer and switched back to Word. Another Crash. We're at 6 crashes today.
@JosephWright the PC is newly set-up for me. Win10 is now installed for a week. The only program crashing upon losing and regaining focus is Word...
@Skillmonlikestopanswers.xyz I don't use word, but I'm rather certain, that if word would normally crash every 5 minutes it would be known. Which reminds me: my editor crashed last week when I tried to load an external tex file. The author investigated and found out that the tex file had two lines starting with 3900 spaces and that was something he hadn't expected - the code assumed at most 1000 spaces.
I'm starting to mirror my crash-log in a .txt file so that I can add the crashes there immediately and only later add them to the Word file
@JosephWright ah. So word managed to corrupt its own config file with the following changes made by the user to the default settings: Changed the colour theme from the built-in "bunt" to the built-in "dunkelgrau".
@UlrikeFischer vim also has problems with lines of such length: It doesn't crash, but after 3000 characters syntax highlighting stops working and everything is colored in default colors. Quite a pain if you work with auto-generated JSON files or stuff like that.
@MarcelKrüger the problem here was that winedt tried to autowrap the long lines while preserving the start space. But the author said he fixed it, in the next release it won't crash anymore.
Another crash! It's pretty reproducible now. Everytime Word loses and regains focus it crashes (except for the one time when it crashed while I tried to save and exit).
I begin to really despise Word. Before it was just a light dislike as it produced ugly documents. Now that dislikes is forged and molded into a strong hatred.
@AlainMatthes depends. In Windows most likely this crashes everything.
@AlainMatthes but on a usable OS this shouldn't be any problem
@UlrikeFischer @Skillmonlikestopanswers.xyz that is the name. I've a problem with the han library of the pgfornament-han package. I would like rename the han folder with -han and the ornaments han1.pgf with -han1.pgf etc. It was a simple solution to my problem
16:49 I got my ninth crash today. Word doesn't crash on an empty document when switching windows. But as soon as I type in a sentence and switch away and back -> CRASH
@PauloCereda yes, please open it, type: "Burn in hell you bugfest of an abominational software!" delete it. Format your drive. Fill your disk with random content completely. Reinstall your OS without Word.
@AlainMatthes While all systems I know work fine with such files, they are a pain to work with from any UNIX based shell. So distributing them is often a bad idea. (That's probably the reason CTAN denies it too)
@MarcelKrüger I'm trying to integrate LianTze's han library (pgfornament-han) into my pgfornament package. But LianTze changed part of the code and I can't load the library without changing the name.
ABSOLUTELY NO F*CKING INFORMATION ON THE SUBJECT!!!!
@UlrikeFischer in the meantime I figured as much. There I have the entry "Microsoft Office Alerts" which holds absolutely no information on any of the crashes.
@AlainMatthes So you want to upload a changed version of existing files to CTAN? I have a feeling that you will get more opposition then just for the names... Especially what happens if both versions are loaded? Did you reach out to LianTze to ensure that your versions are consistent? Anyway, if you really want to, you can just use a longer prefix. Maybe pgfornament-?
@AlainMatthes that is OS dependent you can do that in any posix (linux/mac) etc filesystem but it's a bit antisocial as it will catch users out with ls -xyz being taken as the option named xyz not the file (you can avoid that but many users and scripts willtrip up)
@Skillmonlikestopanswers.xyz Hi! As much as I hate Word, it has been a lot of time since it crashed so spectacularly on me. Something is wrong over there --- even my installation under Wine is more or less usable.
@Rmano you don't say? :) Yes, something is very wrong here. I figured as much. But 10 crashes on a single day. Crashing because you it lost focus and regained it. One should think that this bugware should be more stable.
@Skillmonlikestopanswers.xyz Normally the problem is that a round trip of a .docx document between two even minor different Word versions (for example, a minor release or a change in language) makes all images and formatting go around like crazy...
@Skillmonlikestopanswers.xyz Yes :). Mine (University 365 license) works ok in a virtual machine. Although I normally cheat and do all my editing in LibreOffice...
@AlainMatthes ^^^ you can guard the special filenames with -- and other ways but the vast majority of scripts expecting a filename will do the ls -xyz version and fail if the filename starts with -
@AlainMatthes Who are "we" in this context? Also my concern wasn't that your files are not loaded, but that users of pgfornament-han probably want to load the real pgfornament-han package and not some modified files.
@MarcelKrüger LianTze and me. The problem is complex because pgfornament-han uses pgfornament. It even changes some of my macros. If my package is too much modified, his doesn't work anymore.
@AlainMatthes French and German give trick fake genders to inanimate objects to confuse the English, we just give genders to people (and ships:-) so it should be easier!
@Rmano sure if you know it is there, but it is the million scripts you have that say somecommand * expecting to pick up all the files in the directory that then fail.
@yo' not in normal conversations about commercial flights, you would refer to a plane as "it" only perhaps in single seater planes where the pilot has special attachment to a specific plane might be referred to by gender and name
This morning's sad news flash -- a tiger at the Bronx Zoo has caught the COVID-19 virus from an asymptomatic zookeeper. So all cat lovers and keepers, practice social distancing.
@AlanMunn -- Memories of the Severn Bridge: drive onto the bridge in our rental car, start noisy hailstorm; reach the other side, stop hailstorm. (We left Wales by another route.)
@AlanMunn -- We only encountered a gentle mist. Very atmospheric. Views softened like they are in the Smoky Mountains. (Wales is someplace I'd like to go back to.)
@DavidCarlisle I think the 'not usually' applies to all modes of transport. Using 'she/her' with them usually requires some context of affection, usually on the part of the owner or someone closely related to it. (Discounting, of course, people who actually name their cars, in which case the pronoun matches the name.)
@AlanMunn -- Counterexample: We have two cars, both named after male dragons. But we still refer to them as "she". (In my case, this is probably influenced by the fact that my father was navy. In some things, I don't claim to be logical.)
@CarLaTeX -- We used to have a cat that liked nothing more than to stalk back and forth on the edge of the bathtub (when someone was in it), and from time to time he'd dip a paw in. Fortunately, his balance was good, and he never fell in. Since he had very long fur, he would have been a really pathetic scrawny mess if he had gotten all wet.
@AlanMunn -- If this had been necessary in the environment in which I used to work, I would have embedded it in \text{\huge$...$} since every available size had compatible math font sizes defined properly. (But that's not a universal practice.)
@CarLaTeX -- Quite possibly, but he never found any. (It did take me a while to get used to it though. He still had claws.)
@AlanMunn it doesnt really have to be global, you just need to set the fonts locally, I could suggest some code later if needed but Im on a call for the next hour
Being fed up with Word has its upsides. I think I can get the equal signs splitting code in expkv (and hence in \keys_parse:NNn) to around 80% on average compared to the current run-time.
I'm pretty sure the \keys_parse:NNn can be even a bit faster, as it doesn't resplit for the two-equal signs case but just throws an error.
The code looks pretty messy though and needs 31 lines more :)
Currently just in an evaluation form in which I can benchmark it, it misses the forwarding to the next parsing steps and instead has some commented test-strings.
@PauloCereda /killer rabbit hug, slowly chewing on the duck
@DavidCarlisle -- Yes, heard that a bit ago on the radio. Whatever one thinks of his governing style or policies, it's unfortunate. Let's hope his "backup" is up to speed.