Battle of Lleida (1642)
The Battle of Lleida was a battle fought on October 7, 1642 during the Catalan Revolt.
.jpg)
History
After a series of victories in 1642 the Franco-Catalan army under the command of Philippe de La Mothe-Houdancourt controlled almost the whole of Catalonia, including Lleida. King Philip IV of Spain ordered Diego Felipez de Guzmán, Marquis of Leganés to assemble an army from Tarragona and Zaragoza to retake Lleida. La Mothe positioned his smaller army in the Llano de las Forques and defeated the Spanish army. After the victory, the French Army besieged Tortosa, but was forced to withdraw.
gollark: That makes you a BLASPH.
gollark: Ah. I see.
gollark: <@&198138780132179968> <@270035320894914560>/aus210 has stolen my (enchanted with Unbreaking something/Mending) elytra.I was in T79/i02p/n64c/pjals' base (aus210 wanted help with some code, and they live in the same place with some weird connecting tunnels) and came across an armor stand (it was in an area of the base I was trusted in - pjals sometimes wants to demo stuff to me or get me to help debug, and the claim organization is really odd). I accidentally gave it my neural connector, and while trying to figure out how to get it back swapped my armor onto it (turns out shiftrightclick does that). Eventually I got them both back, but while my elytra was on the stand aus210 stole it. I asked for it back and they repeatedly denied it.They have claimed:- they can keep it because I intentionally left it there (this is wrong, and I said so)- there was no evidence that it was mine so they can keep it (...)EDIT: valithor got involved and got them to actually give it back, which they did after ~10 minutes of generally delaying, apparently leaving it in storage, and dropping it wrong.
gollark: Someone had a problem with two mutually recursive functions (one was defined after the other), so I fixed that for them. Then I explained stack overflows and how that made their design (`mainScreen` calls `itemScreen` calls `mainScreen`...) problematic. Their suggested solution was to just capture the error and restart the program. Since they weren't entirely sure how to do *that*, their idea was to make it constantly ping their webserver and have another computer reboot it if it stopped.
gollark: potatOS is also secure <@!290217153293189120> ke
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.