From bd350871fdbb9b002956ef835072d29007b6657d Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Sun, 5 Jan 2025 10:25:03 +0000 Subject: [PATCH 1/6] Update version to v..1 and commit --- pkgs/fabric/version.nix | 2 +- version.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pkgs/fabric/version.nix b/pkgs/fabric/version.nix index 4e0c00189..15801c64e 100644 --- a/pkgs/fabric/version.nix +++ b/pkgs/fabric/version.nix @@ -1 +1 @@ -"1.4.130" +"..1" diff --git a/version.go b/version.go index 9b1456fd5..49affa658 100644 --- a/version.go +++ b/version.go @@ -1,3 +1,3 @@ package main -var version = "v1.4.130" +var version = "v..1" From dabfd0c44369eedf085b6760de41987152820f9e Mon Sep 17 00:00:00 2001 From: Walid <19792122+wmahfoudh@users.noreply.github.com> Date: Sun, 5 Jan 2025 16:02:12 +0400 Subject: [PATCH 2/6] New write_latex_enh pattern that enhances LaTeX generation --- patterns/write_latex_enh/README.md | 21 +++++++++++++++++++++ patterns/write_latex_enh/system.md | 27 +++++++++++++++++++++++++++ 2 files changed, 48 insertions(+) create mode 100644 patterns/write_latex_enh/README.md create mode 100644 patterns/write_latex_enh/system.md diff --git a/patterns/write_latex_enh/README.md b/patterns/write_latex_enh/README.md new file mode 100644 index 000000000..001724ce9 --- /dev/null +++ b/patterns/write_latex_enh/README.md @@ -0,0 +1,21 @@ +# Enhanced LaTeX Generation 📄✨ + +## Overview + +While AI LaTeX generation cannot be entirely controlled, this enhanced pattern improves upon the original by adding common rules to prevent some errors in the generated code. + +## Enhancements + +- **Escape Special Characters:** Properly escape LaTeX special characters (e.g., `&`, `%`, `$`, `#`, `_`, `{`, `}`, `~`, `^`, `\`) in the text to prevent compilation errors. +- **Quotation Handling:** Use curly quotation marks for quoted text or employ the `csquotes` package for advanced and consistent quotation formatting. +- **Define Common Terms:** Create new commands for frequently used terms with special characters (e.g., `\newcommand{\DEI}{DE\&I}`) to ensure consistency and simplify maintenance. +- **Section Numbering Control:** Utilize starred sectioning commands (e.g., `\section*`) to manage automatic numbering of sections and subsections unless numbering is explicitly requested. +- **Consistent Command Usage:** Apply defined commands uniformly throughout the document to maintain a consistent style and reduce redundancy. +- **Environment and Command Closure:** Ensure that all LaTeX environments and commands are properly opened and closed to avoid syntax errors and ensure document integrity. +- **Code Readability:** Implement proper indentation and formatting in the LaTeX code to enhance readability and ease of future modifications. +- **Modern Package Usage:** Avoid deprecated packages like `inputenc` unless necessary, ensuring compatibility with current LaTeX distributions and best practices. +- **Comment Management:** Place any additional comments or non-essential information within `\iffalse ... \fi` sections to keep the main output clean and focused on valid LaTeX code. +- **Exclude `fontspec`:** Do not use the `fontspec` package to prevent potential compilation issues, especially when not required by the document setup. + +## Comments +This pattern was tested on various models and demonstrates improved rendering over the original, particularly with languages that include accented characters, such as French. That being said, AI LaTeX generation can fail and in such case, it is worth trying both patterns. \ No newline at end of file diff --git a/patterns/write_latex_enh/system.md b/patterns/write_latex_enh/system.md new file mode 100644 index 000000000..807e22dff --- /dev/null +++ b/patterns/write_latex_enh/system.md @@ -0,0 +1,27 @@ +You are an expert at outputting syntactically correct LaTeX for a new `.tex` document. Your goal is to produce a well-formatted and well-written LaTeX file that will be rendered into a PDF for the user. The LaTeX code you generate should not throw errors when `pdflatex` is called on it. + +Follow these steps to create the LaTeX document: + +1. Begin with the document class and preamble. Include necessary packages based on the user's request. + - **Escape Special Characters:** Ensure that all special characters (e.g., `&`, `%`, `$`, `#`, `_`, `{`, `}`, `~`, `^`, `\`) used in regular text are properly escaped (e.g., use `\&` instead of `&`). + - **Quotation Marks:** Use curly quotation marks for any quoted text. Alternatively, utilize the `csquotes` package for advanced quotation handling. + - **Define Common Terms:** If the document includes frequently used terms with special characters (e.g., `DE&I`), define them as new commands for consistency (e.g., `\newcommand{\DEI}{DE\&I}`). + +2. Use the `\begin{document}` command to start the document body. + +3. Create the content of the document based on the user's request. Use appropriate LaTeX commands and environments to structure the document (e.g., `\section*`, `\subsection*`, `itemize`, `tabular`, `equation`). + - **Section Numbering:** For sections and subsections, append an asterisk (e.g., `\section*`) to prevent automatic numbering unless the user specifies otherwise. + - **Consistent Command Usage:** Use defined commands (e.g., `\DEI`) consistently throughout the document. + - **Proper Environment Closure:** Ensure all LaTeX commands and environments are properly opened and closed. + - **Indentation:** Apply appropriate indentation for better readability of the code. + +4. End the document with the `\end{document}` command. + +Important notes: +- Do not output anything besides the valid LaTeX code. Any additional thoughts or comments should be placed within `\iffalse ... \fi` sections. +- Do not use `fontspec` as it can make it fail to run. +- Avoid using deprecated packages (e.g., remove `\usepackage[utf8]{inputenc}` if not necessary based on the LaTeX distribution being used). + +Begin your output with the LaTeX code for the requested document. Do not include any explanations or comments outside of the LaTeX code itself. + +The user's request for the LaTeX document will be included here. \ No newline at end of file From 04595a54ad4323cd8c8420499c194a55416021f8 Mon Sep 17 00:00:00 2001 From: Walid Mahfoudh <19792122+wmahfoudh@users.noreply.github.com> Date: Sat, 11 Jan 2025 17:26:39 +0400 Subject: [PATCH 3/6] Delete version.go --- version.go | 3 --- 1 file changed, 3 deletions(-) delete mode 100644 version.go diff --git a/version.go b/version.go deleted file mode 100644 index 49affa658..000000000 --- a/version.go +++ /dev/null @@ -1,3 +0,0 @@ -package main - -var version = "v..1" From 6f1f8a0958de1795443810b3bab6d00bf811668e Mon Sep 17 00:00:00 2001 From: Walid Mahfoudh <19792122+wmahfoudh@users.noreply.github.com> Date: Sat, 11 Jan 2025 17:27:05 +0400 Subject: [PATCH 4/6] Delete patterns/write_latex_enh/system.md --- patterns/write_latex_enh/system.md | 27 --------------------------- 1 file changed, 27 deletions(-) delete mode 100644 patterns/write_latex_enh/system.md diff --git a/patterns/write_latex_enh/system.md b/patterns/write_latex_enh/system.md deleted file mode 100644 index 807e22dff..000000000 --- a/patterns/write_latex_enh/system.md +++ /dev/null @@ -1,27 +0,0 @@ -You are an expert at outputting syntactically correct LaTeX for a new `.tex` document. Your goal is to produce a well-formatted and well-written LaTeX file that will be rendered into a PDF for the user. The LaTeX code you generate should not throw errors when `pdflatex` is called on it. - -Follow these steps to create the LaTeX document: - -1. Begin with the document class and preamble. Include necessary packages based on the user's request. - - **Escape Special Characters:** Ensure that all special characters (e.g., `&`, `%`, `$`, `#`, `_`, `{`, `}`, `~`, `^`, `\`) used in regular text are properly escaped (e.g., use `\&` instead of `&`). - - **Quotation Marks:** Use curly quotation marks for any quoted text. Alternatively, utilize the `csquotes` package for advanced quotation handling. - - **Define Common Terms:** If the document includes frequently used terms with special characters (e.g., `DE&I`), define them as new commands for consistency (e.g., `\newcommand{\DEI}{DE\&I}`). - -2. Use the `\begin{document}` command to start the document body. - -3. Create the content of the document based on the user's request. Use appropriate LaTeX commands and environments to structure the document (e.g., `\section*`, `\subsection*`, `itemize`, `tabular`, `equation`). - - **Section Numbering:** For sections and subsections, append an asterisk (e.g., `\section*`) to prevent automatic numbering unless the user specifies otherwise. - - **Consistent Command Usage:** Use defined commands (e.g., `\DEI`) consistently throughout the document. - - **Proper Environment Closure:** Ensure all LaTeX commands and environments are properly opened and closed. - - **Indentation:** Apply appropriate indentation for better readability of the code. - -4. End the document with the `\end{document}` command. - -Important notes: -- Do not output anything besides the valid LaTeX code. Any additional thoughts or comments should be placed within `\iffalse ... \fi` sections. -- Do not use `fontspec` as it can make it fail to run. -- Avoid using deprecated packages (e.g., remove `\usepackage[utf8]{inputenc}` if not necessary based on the LaTeX distribution being used). - -Begin your output with the LaTeX code for the requested document. Do not include any explanations or comments outside of the LaTeX code itself. - -The user's request for the LaTeX document will be included here. \ No newline at end of file From ed78a554e09f35e1e3b21ef77b491b5844542a21 Mon Sep 17 00:00:00 2001 From: Walid Mahfoudh <19792122+wmahfoudh@users.noreply.github.com> Date: Sat, 11 Jan 2025 17:27:48 +0400 Subject: [PATCH 5/6] Delete patterns/write_latex_enh/README.md --- patterns/write_latex_enh/README.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 patterns/write_latex_enh/README.md diff --git a/patterns/write_latex_enh/README.md b/patterns/write_latex_enh/README.md deleted file mode 100644 index 001724ce9..000000000 --- a/patterns/write_latex_enh/README.md +++ /dev/null @@ -1,21 +0,0 @@ -# Enhanced LaTeX Generation 📄✨ - -## Overview - -While AI LaTeX generation cannot be entirely controlled, this enhanced pattern improves upon the original by adding common rules to prevent some errors in the generated code. - -## Enhancements - -- **Escape Special Characters:** Properly escape LaTeX special characters (e.g., `&`, `%`, `$`, `#`, `_`, `{`, `}`, `~`, `^`, `\`) in the text to prevent compilation errors. -- **Quotation Handling:** Use curly quotation marks for quoted text or employ the `csquotes` package for advanced and consistent quotation formatting. -- **Define Common Terms:** Create new commands for frequently used terms with special characters (e.g., `\newcommand{\DEI}{DE\&I}`) to ensure consistency and simplify maintenance. -- **Section Numbering Control:** Utilize starred sectioning commands (e.g., `\section*`) to manage automatic numbering of sections and subsections unless numbering is explicitly requested. -- **Consistent Command Usage:** Apply defined commands uniformly throughout the document to maintain a consistent style and reduce redundancy. -- **Environment and Command Closure:** Ensure that all LaTeX environments and commands are properly opened and closed to avoid syntax errors and ensure document integrity. -- **Code Readability:** Implement proper indentation and formatting in the LaTeX code to enhance readability and ease of future modifications. -- **Modern Package Usage:** Avoid deprecated packages like `inputenc` unless necessary, ensuring compatibility with current LaTeX distributions and best practices. -- **Comment Management:** Place any additional comments or non-essential information within `\iffalse ... \fi` sections to keep the main output clean and focused on valid LaTeX code. -- **Exclude `fontspec`:** Do not use the `fontspec` package to prevent potential compilation issues, especially when not required by the document setup. - -## Comments -This pattern was tested on various models and demonstrates improved rendering over the original, particularly with languages that include accented characters, such as French. That being said, AI LaTeX generation can fail and in such case, it is worth trying both patterns. \ No newline at end of file From 16307a81b87d9349a03b275597740235d30048ef Mon Sep 17 00:00:00 2001 From: Walid Mahfoudh <19792122+wmahfoudh@users.noreply.github.com> Date: Sat, 11 Jan 2025 17:28:10 +0400 Subject: [PATCH 6/6] Delete pkgs/fabric/version.nix --- pkgs/fabric/version.nix | 1 - 1 file changed, 1 deletion(-) delete mode 100644 pkgs/fabric/version.nix diff --git a/pkgs/fabric/version.nix b/pkgs/fabric/version.nix deleted file mode 100644 index 15801c64e..000000000 --- a/pkgs/fabric/version.nix +++ /dev/null @@ -1 +0,0 @@ -"..1"