shame this was voted off topic!

@DavidCarlisle Did you have an answer in mind?

@TeXnician no:-)

@TeXnician @DavidCarlisle is only familiar with MS Pain(t) and not face paint ;-)

@ChristianHupfer MS Pain? Do they have a new truth policy?

@ChristianHupfer ^^

@DavidCarlisle very .... 'nice' ;-)

@ChristianHupfer a realism that you'd never get with tikz

@DavidCarlisle A level of realism nobody (except of you) tries to achieve ... ;-)

@ChristianHupfer I shall take that as a compliment

@DavidCarlisle It was a comment, not a compliment :-P

@TeXnician: That's one of the 'exploiters' ;-) He's a user for more than 2 years ;-)

@ChristianHupfer You're right, didn't notice it. At least I think its funny that he answered his question some time ago (about the same notation).

@TeXnician Yes, I wondered already...

@ChristianHupfer Probably he dislikes the array solution...

@TeXnician: Let me cite Pulp Fiction: The path of the asking man is depicted on both sides ... with strange questions and errant X for Y requests ;-)

@DavidCarlisle picture mode strikes again

@DavidCarlisle Let's propose this for tate.org.uk/visit/tate-modern

Everyone seen the \write18 question?

@JosephWright both.

@egreg It's too modern even for the Tate ;-)

@JosephWright That's the problem with MiKTeX: new versions are deployed without waiting for helper packages (shellesc or luatex85).

@egreg Yes, but as I said it's down to Christian alone

@egreg Also, writing today they are available

@DavidCarlisle ROFL.... I'm wondering when someone asks for a Tex's \hat: it.m.wikipedia.org/wiki/Tex_Willer

@egreg @JosephWright: Sorry but as I wrote in the comment: this is not miktex specific. Exactly the same question just came two days ago for texlive 2016: tex.stackexchange.com/questions/365777/….

@PauloCereda LOL

Hello

I need help in finding text to copy

Here how it looks like^

Sorry if it is off-topic

Anyone ?

@UlrikeFischer That's people not reading the documentation.

Hello @egreg I saw you on math.se

Alot times

@Fawad Ciao!

@egreg can I ask that on main site? (On topic?) It will get attention soon

@StefanKottwitz Just kicked the third wave of spam at LC, within the last eight hours. :-(

@Fawad We usually deal with good questions very quickly

@StefanKottwitz Next wave just started.

@Johannes_B Thanks! I can only prevent bots not human spammers. If q&a captcha is broken and programmed to bots, I usually change it (see it when such waves come in repeatedly)

@StefanKottwitz Five or six posts within a few minutes. I kicked them. Nothing to worry :-)

@UlrikeFischer On the LuaTeX/MiKTeX/TL business, I have a feeling we are at cross-purposes. The fact that some macro code hasn't been update so is broken in MiKTeX and TL is entirely true. What's different between TL and MiKTeX is the former has a fixed cycle for binary changes, so as a macro provider I can 'know' which engines I have to support and when to upload to CTAN to do that.

@UlrikeFischer I'm not complaining about MiKTeX, simply observing that the approach is different

@JosephWright I think a two week delay would be good before updating binaries. So package authors can amend stuff. Right now, we (helpers) wake up and have several issues by users because LuaTeX has changed.

A bit of testing would be nice.

@JosephWright I know the difference and also the dangers (and benefits) of the "under-the-year" updates of miktex. That's why I often keep an eye on possible conflicts and either warn package authors or Christian. But in this case it wasn't relevant. The question and the complains of the OP would have been exactly the same if miktex had updated its binaries at the same time as texlive 2016. It would be different if luaotfload would break but this would be good as it would warn texlive 2017 ;-)

Just remembering the biblatex 3.3 update.

@Johannes_B Oh, don't start!

@Johannes_B There is a delay -- new binaries are first in miktex next and texlive is doing a pretest. And @DavidCarlisle is doing a lot of testing with the development versions of luatex and when he reports problem I often check the impact on miktex.

@Johannes_B @DavidCarlisle and I have (more-or-less) 'burning edge' LuaTeX on the go much of the time for exactly this reason

@Moriambar Google maps says that l'm 50km from the crucible and I could walk there in 7 hours , think l should go?

@JosephWright But that has absolutely no impact if a user says: I have been using LaTeX for decades, had to reinstall and now \documentstyle gives some strange warnings.

@DavidCarlisle nope, by then the games will have ended

@DavidCarlisle unless you wan to stay all of next week waiting for the final: in that case a 7 hour walk could be worthy

Software update. Be aware of changes.

@TeXnician 1 command and lots of documentation are between me and the next release of typoaid does almost all I wanted to do, except vertical suggestions :)

@Moriambar Vertical suggestions? Do you want to reimplement all aspects of KOMAs typearea calculations?

@Johannes_B True, but we do worry about 'I took this LaTeX document that seems fine with pdfTeX and switched to LuaTeX and all sorts of issues arose' and 'I had this working LuaLaTeX document that is now broken'

@TeXnician I don't know anything about KOMA except they break with many packages, and that they're mainly used by german-speaking people. I just want to suggest a couple of heights given a width, following some of the masters. My package only prints suggestions and calculations, does not do anything for the actual typesetting, which is left to the author

@Moriambar Ah okay, I thought you wanted to give suggestions about optimal text height or something like that.

@Moriambar there are some german-speaking-people around here ;)

@Johannes_B You don't see the list of unexpected changes in the LaTeX2e test suite with each update :)

@JosephWright No, i don't :-)

@Johannes_B We've had a few 'interesting' sets

@JosephWright you should go into politics

@TeXnician I don't see your point

@Moriambar that was just an observation.

@TeXnician anyway, since I give suggestions about the textblock width, based on the current font, in order to obtain specific char/row ratio, it could be nice, giving a column width a font and a baselineskip, to have suggestions about the textblock height, in the sense to obtain a height/width proportion or an integer row/height ratio

@Moriambar you're totally right.

^^ Have you seen this?

@TeXnician

:36896284 nice message (what was that path?) ;)

@TeXnician sorry, -.-'

@TeXnician he's got a point

@Moriambar Interesting, especially the dups (66 chars per row and chars per row 66) :D

@TeXnician you would be interested in the value of the other columns in that row :D

@Moriambar of course, but I did not see those questions in comparison. didn't expect such huge difference in votes.

@TeXnician I've seen the first one.

@Moriambar probably. The other 65 chars ;)

@TeXnician lol

@Moriambar Me too. But not the second one.

@Moriambar personal thought: could you please add a @{} at the beginning and end of your column specification (removes left and right overhead).

@TeXnician I like the left and right overhead

I think they make the table look way better

@Moriambar It's personal taste, of course (as I said). Probably I'm used to the overheadless version since I always have too broad tables and have to fit it into textwidth.

@TeXnician I'm usually inclined to keep the padding around the first and last column if the table is at natural width, removing it if it is set to the column width.

@egreg yes I agree too. There's almost always no point in having overhead in a table that's smeared, cramped or even correctly set at full column width

@DavidCarlisle did you go to sheffield? I will see you in the crowd?

can anyone tell me how I can get the font size via expl3? Actually I don't know how to calculate it even in L2, but expl3 is what I'm looking for. I'll just leave this here while I watch Robertson

@cfr No worries. I figured out a way to do what I wanted.

@Moriambar The fontsize (in pt) is stored in \f@size.

@AlanMunn is it called the same way in the expl3 cunning schemas?

@Moriambar I have no idea (which is why I said nothing about it). I don't think expl3 seeks to rename everything in the LaTeX kernel though. But that's a question for others to answer.

@AlanMunn thanks. I'll wait for the expl3 gurus, I think it's nice to know. But the 11th frame has begun

@Moriambar If you search for f@size in interface3.pdf nothing shows up, so I suspect it hasn't got an L3 name.

@AlanMunn there's no guarantee: the documentation does not report every TeX/LaTeX command they have translated; and a command with an @ looks so ugly in l3 code

but thanks

maybe @egreg or @JosephWright could give an expl3 explanation. Worst case I will use \f@size

@Moriambar highlevel commands like the font selection sheme hasn't yet been implemented in expl3, so you will have to live with the "ugly" @ in \f@size.

@Moriambar Unreleased code (just a straight copy of the current with new names) is in the LaTeX3 repo but that's really not ready for release

@JosephWright thanks, how can I be notified when this part is released?

@Moriambar no, I came home (just got in:-)

@Moriambar LaTeX-L mailing list the official source: at present I think 'some way off' is the best view on this

@JosephWright can anyone subscribe or is it reserved?

@DavidCarlisle pity you should've seen the marvelous match (ongoing) between robertson and fu

@Moriambar I'm half watching that now

@Moriambar welcome to my world when dealing with counter stuff and LaTeX2e, but writing code with expl3, i.e. xassoccnt, for example. 'A lot' of @ to endure ;-)

@Moriambar if you don't like the @ you only need use it once. \def\foo_get_font_size:{\f@size} then use \foo_get_font_size: as a 0-argument function to return the current font size

@Moriambar Anyone can join: it's the official discussion list (there is a closed list for the team)

@DavidCarlisle \zzz_get_font_sizzzzze: looks better ;-)

@UlrikeFischer sorry, you are of course correct.

@DavidCarlisle great! I understand I can redefine it but it's ugly nevertheless :)

@ChristianHupfer :)

@UlrikeFischer I agree

@JosephWright I'm lazy can you give me a link please? (of course the team is a closed list)

@Moriambar the whole point of expl3 is a compromise between a pure latex3 code base (which is cleaner code but has compatibility issues and missing functionality) and the functionality and compatibility for the existing 2e infrastructure. So dealing with the occasional @ isn't ugliness, it is part of the core design of the expl3 system

@Moriambar mailing list instructions: latex-project.org/latex3/code

TFW Just as you finish a very instructive "how to solve your own problem by constructing a minimal example" answer the OP deletes the question.

Good evening to everybody.

@ChristianHupfer Hi Christian.

@DavidCarlisle I understand. All part of the transition, I guess?

@DavidCarlisle thanks

@Moriambar, @ChristianHupfer, @egreg, @DavidCarlisle how is my work?

@DavidCarlisle It's a token list variable, not a function.

@DavidCarlisle. @Moriambar, @egreg, @ChristianHupfer How is my work?

@egreg Hiiiii dearest Prof.

@Sebastiano Seems nice!

@Sebastiano I'd use italics for emphasis, rather than boldface

i.stack.imgur.com/Kwjnf.png I have changed textcolorbox

@egreg I have not understand, What change should I do according to your advice? My source is very long. I would also need your help. I also asked a question about 15 minutes.

@egreg I wondered about that but probably it's more of a function accessing the token list variable (that is named \f@size for historical reasons.

@egreg i have realized the figures with adobe illustrator

@egreg you could \let a tl variable to \f@size but that's not what you want if you want to track the size after it changes

@DavidCarlisle \use:c {f@size}

@egreg Do you think my question is as clear or strange as ever? tex.stackexchange.com/questions/366290/…

@Sebastiano I'll look at it later

@egreg OKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK

@Sebastiano it's clear enough but probably a duplicate of the one linked in comments

@DavidCarlisle with mt2pro lite and times adding any charachter I have seen no duplicate.

@DavidCarlisle I looked at everything about the various links. But I'm not as good as you.

@Sebastiano I didn't look in detail but the specific fonts shouldn't affect things, there is a general question on how to add symbols from a different font

@DavidCarlisle cough

@ChristianHupfer still coughing? It's a recurring condition then :)

@Moriambar Coughed for other reasons, this time ;-) You did not provoke coughs today

@DavidCarlisle Help me. It's a gift for my university professor.

@ChristianHupfer christian i have changed tcb are you see?

I have to close my battery is low. Thank you so much for everyone hello

@Sebastiano I am seeing images, but I don't see tcolorbox/tcb content directly

@egreg token lists are a part of l3 that still I don't get… I will get there ;)

@Moriambar they are just an abstraction of \def\zz{abc}, that is: macros with no parameters just holding a list of tokens

@DavidCarlisle ooh so basically I've done many things wrong

@Moriambar ?

@DavidCarlisle got plenty of them, none marked as token list

@DavidCarlisle I will correct those things later on, now I'm concerned in printing "\bask\bfseries" which is in #2

and I at most get out bask with \cs_to_str:N#2

@Moriambar N takes a single token and \bask\bfseries` is two you could just use \detokenize{#2} but we probably have an l3 name for that..

@DavidCarlisle that's interesting, because it will definitely cover the only minor problem now: if one gets two switches (e.g. a font change and a switch) it would be nice to display both (either as commands or as command names)

(I haven't found detokenize in l3)

@Moriambar @DavidCarlisle \tl_to_str:n is \detokenize.

@UlrikeFischer great

@UlrikeFischer thanks I knew it was there somewhere:-)

@UlrikeFischer removing backslashes is too much to ask, I guess… well if it is, no problem: next version ;)

\tl_remove_all:Nn ?

@Moriambar why no backslashes? what could you do with baskbfseries ?

@DavidCarlisle it's for display

@Moriambar yes but \bask\bfseries is a lot more understandable than baskbfseries

@DavidCarlisle but it's ok, thanks so much (and @UlrikeFischer too). I'll call it a night

@DavidCarlisle Thinking about it you're right. I always forgot that the one reading things is the same one who wrote \bask\bfseries so he should understand what they stand for

@TeXnician @ChristianHupfer code is frozen! Now with the new improved documentation for version 0.3.6 and then to ctan with the update :)

@Moriambar Ah... go ahead

@ChristianHupfer what? you're not a typoaid fanboy? :P

@JosephWright Feature request: make nfssext-cfr obsolete`. Please ;).

@Moriambar Any answer to your question will be wrong, I fear :D

@ChristianHupfer you may be right. Let me rephrase that: are you not a strong supporter of typoaid?

@Moriambar I am a strong supporter in the sense that I find it very useful to query the used font.

@Moriambar: Oy, you mentioned me in the documentation without asking /sob

@Moriambar: Did @DavidCarlisle force you to write: "They cannot be blamed for anything that may be wrong with this package" ;-)

@cfr Here's what I was going to ask you about. I wanted to circle a node but keep the tree nodes looking identical, so adding draw=red,circle to a node didn't work. Here's what I ended up doing. Is there a better way?

\documentclass{article}
\usepackage[linguistics]{forest}
\forestset{barrier/.style=
{tikz={\node[draw=red,circle,thick,fit=(),inner sep=0pt,outer sep=0pt]{};}},
default preamble={for tree={inner sep=0pt,s sep=.25in}}}
\begin{document}
\begin{forest}
[AP [BP [B ]] [CP,barrier [C ]]]
\end{forest}
\end{document}

@ChristianHupfer No. I felt that I wouldn't put there people who helped concretely and directly with the development but people I felt should be acknowledged for the fact that I was able to write that code. It seemed to me honest to put a disclaimer, since otherwise one could say that I did wrong by mentioning him. I'll remove the acknowledgements then, from the future versions, since there seems to be some ambiguity

but it's tomorrow's job, I'll call it a night!

@Moriambar I am still working on improvement of xassoccnt. I found in my documentation that I mentioned macros that should be in the package, but I didn't find them any more. I have accidentally removed them at state 5 release before current version and nobody noticed .... the macros must be very important then.

@Moriambar I'm not sure if @ChristianHupfer is complaining seriously, but your acknowledgement seems perfectly appropriate to me. (But he and I disgree frequently it seems, so YMMV. :) )

@AlanMunn In this case I should really oppose the mentioning then ;-)

@ChristianHupfer :D

@AlanMunn I agree with you this time that we disagree very often on many occasions

@ChristianHupfer LOL what a dilemma for you.

@ChristianHupfer I guess so

@AlanMunn thanks. I'm confused right now, though, on what to do. I'll substitute @ChristianHupfer with Don Knuth, I guess, and leave the others. Sorry @ChristianHupfer, I meant no disrespect

@Moriambar Oh, you're replacing me by Don Knuth. I feel deeply honoured.... wait This means that I am just substitutable by such blokes? ;-)

@Moriambar: In fact, I asked only one of the users I mentioned in my package, @PauloCereda remembers I think :-P

@Moriambar For the next version: variables used globally (with \dim_gset:Nn, for instance) should be prefixed by g, not l: so \g__typoAid_ExHeight_dim and so on. Private functions should be \__typoAid... (two underscores). Don't use \ProvideDocumentCommand, but \NewDocumentCommand.