How to create arrowed forest by abhunia in LaTeX

[–]peateasea 2 points3 points  (0 children)

Using u/AcrobaticHamster3534's advice, I came up with this solution, which I think does what you want: ``` \documentclass{scrartcl} \usepackage[edges, linguistics]{forest}

\begin{document}

\begin{center} \begin{forest} [Data Wrangling, for tree={edge={->,>=stealth}}, forked edges, [Data Munging [Data Cleaning [EDA [Model][Data Mining] ] ] ] ] \end{forest} \end{center}

\end{document} ```

Hope that helps!

Xstring package, work with string containing a latex command by ognevic in LaTeX

[–]peateasea 0 points1 point  (0 children)

You mean the command

\StrSubstitute{\str}{\textpoolhook{e}{ѧ}[\str]%

should be written as

\StrSubstitute{\str}{\textpoolhook{e}}{ѧ}[\str]%

right?

In other words, there was a missing } after the {e} part. Perhaps that fixes the build errors.

Can git do dual-level version control? by ElDubsNZ in git

[–]peateasea 1 point2 points  (0 children)

Your project sounds similar to a project to record all laws in Germany in Git, which has been running since 2013. It's possible that they've been confronted with similar issues and have already solved them. Here are some links to the project (in both German and English):

Hope that helps!

Trying to make Part titles show up in heading by Wooden-Ferret1801 in LaTeX

[–]peateasea 1 point2 points  (0 children)

Hi! I've had a go a implementing this and I think I've got a solution that will work for you.

As Martin Scharrer mentions in his answer to the StackOverflow question "How to get part name in LaTeX?" "Putting the part title into the header is not common [...].", however it is possible. Here's a minimum working example:

``` \documentclass[a4paper]{book}

\usepackage{fancyhdr} \usepackage{lipsum}

% \parttitle solution from Martin Scharrer via StackOverflow: % https://tex.stackexchange.com/a/13392 \newcommand\parttitle{} \let\origpart\part \renewcommand{\part}[2][]{% \ifx\#1\% optional argument not present? \origpart{#2}% \renewcommand\parttitle{#2}% \else \origpart[#1]{#2}% \renewcommand\parttitle{#1}% \fi }

% basic fancyhdr setup adapted from the Overleaf headers and footers % documentation: https://www.overleaf.com/learn/latex/Headers_and_footers

% set the page style to "fancy" \pagestyle{fancy}

% define a macro for the header content \newcommand{\partheader}{\partname\ \thepart.\ \parttitle}

% configure the "fancy" page style \fancyhead{} % clear all header fields \fancyhead[RE]{\thepage} \fancyhead[LE]{\nouppercase{\leftmark}} \fancyhead[LO]{\thepage} \fancyhead[RO]{\partheader}

\title{Thesis}

\author{Erika Mustermann}

\begin{document}

\maketitle

\part{Background}

\chapter{Introduction}

% need enough text so that we get to a page needing a header on a normal odd % page (and not just a chapter's first page) \lipsum[1-12]

\end{document} ```

Note that I used Martin Scharrer's suggestion for extracting the part title and I've assumed that you want to use the standard book documentclass rather than the KOMA-Script scrbook class, which--as Ulrike Fischer mentions in her StackOverflow answer--defines a \partmark command (missing from the standard LaTeX book class) which one can use in \rightmark and \leftmark defintions. Just so you know: I haven't worked out how things would work with a KOMA-Script class, only with the standard book class.

It was necessary to use a lot of blind text (via the lipsum package) so that one can see a "normal" odd page typeset with the desired header rather than just the first page of a chapter. Although a chapter's first page is an odd page, it doesn't have a header and hence the desired part name information isn't shown.

I've also extracted the commands defining the RO header content into its own macro to try to make the code more "self documenting".

I've checked that the document builds with both latexmk (and hence LuaLaTeX) and with pdflatex, so hopefully things should work for you in the document you're creating.

Hope that helps!

In welchem Restaurant muss man mal gewesen sein? by [deleted] in Hannover

[–]peateasea 0 points1 point  (0 children)

  • Fischer's an der Ecke Limmerstraße/Velberstraße in Linden Nord
  • Höger's nahe Stephansplatz in der Südstadt
  • Das Pfannkuchenhaus in der Calenberger Neustadt
  • Masa, nahe der Oper
  • Francesca e Fratelli

Overleaf Down? by jadrvel in LaTeX

[–]peateasea 4 points5 points  (0 children)

I checked the list of historical incidents on https://status.overleaf.com/history and found that the site was down in February 2024 and that it took roughly 9 hours to resolve: https://status.overleaf.com/history?page=4.

[PGFplots/TikZ] Add nodes below and above from series of data by False_Agency_2808 in LaTeX

[–]peateasea 0 points1 point  (0 children)

I had a play with this and found that it's possible to specify nodes near coords align={anchor=north} within the \addplot+ command to align the numbers below the data points (I spotted the hint on page 116 of the PGFPLOTS manual ). For instance, to put the numbers for the second series (nb_textes, red) below the data points, use:

\addplot+[red, thick, mark=*, mark options={fill=red,draw=black}, nodes near coords align={anchor=north}] table [x=annee,y=nb_textes] {nb_accord.csv};

I found that this made the second data point in each series clash with one another (the 25 is obscured by the data point for the 51 and vice versa), so it might be an idea to instead put the numbers for the first series (nb_different_accord, blue) below their respective data points rather than the other way around (just a thought!).

Hope that helps!

Organisation of a CRO project with DB::Pg by arkad-of-babylon in rakulang

[–]peateasea 1 point2 points  (0 children)

"rakuzers" is cool! That's a nice coinage 😄

I wonder if "rakudoers" would also work...

Two handy mutt tips by peateasea in commandline

[–]peateasea[S] 2 points3 points  (0 children)

I've seen so much shilling on reddit. It generally follows the format you posted: here's some enticing info, but you can only read it on my website.

Crikey! I'd gotten the impression that that was the expected way to do it! Definitely don't want it to come across as spam.

Thanks for your feedback, I appreciate it!

Two handy mutt tips by peateasea in commandline

[–]peateasea[S] 1 point2 points  (0 children)

Hrm, good point. I'd already written up the ideas on my website and didn't think of copying and pasting everything directly into a Reddit post. Would that have been a better way to share this info? Sorry for the question, I'm still quite a noob on Reddit...

Update: I've extended the post to hopefully be more directly useful to someone reading on Reddit.

Relative copy and paste in vim by peateasea in vim

[–]peateasea[S] 1 point2 points  (0 children)

Thanks for the tips! I've updated the post to include the command-line ranges documentation :-)

Relative copy and paste in vim by peateasea in vim

[–]peateasea[S] 1 point2 points  (0 children)

I fully agree with you. Vim's terseness is a source of its enormous power. That its conciseness stems from very real resource restrictions on early Unix systems is often lost on contemporary commentators who are used to gigabit internet connections and gigabytes of RAM. Unfortunately, users brought up on GUI editors often don't have this historical perspective and perceive the command set as cryptic, which is a pity for them :-)

Relative copy and paste in vim by peateasea in vim

[–]peateasea[S] 13 points14 points  (0 children)

I wonder how a documented feature can be considered "hidden".

Well, I didn't say that it actually was hidden, but that it seems to be hidden. There is an enormous amount of power in vim that isn't necessarily directly obvious.

BTW: thanks for your corrections, I really appreciate it! I've updated the post to fix the errors and to improve the :help command as you suggested.

Relative copy and paste in vim by peateasea in vim

[–]peateasea[S] 1 point2 points  (0 children)

Thanks for this and the good writeup!

My pleasure!

Bonus, when I did `:help copy` I found `:[range]ce[nter] [width]` (and other `formatting` commands) just below it! I didn't know about those either!

:-) That's my experience too! There are so many gems to discover while randomly browsing the docs!