<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/pycmd/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/pycmd/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 07 Jan 2023 13:37:51 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/pycmd/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#1a2a</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The PyCmd project has moved to GitHub: &lt;a href="https://github.com/horeah/PyCmd" rel="nofollow"&gt;https://github.com/horeah/PyCmd&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Sat, 07 Jan 2023 13:37:51 -0000</pubDate><guid>https://sourceforge.netd0134e7117295e4220e8b157a3bb02d7f5ccef4b</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#9fa6</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The changes for the Py3 port have now been merged into master and released with 20230107. Thanks @UFO for helping with this!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Sat, 07 Jan 2023 13:03:17 -0000</pubDate><guid>https://sourceforge.netb25099b4cbb5a7a3a1047ef9460a4a27dd07548b</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#66cf</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm of course fine with it, just like you suggested.&lt;br/&gt;
Thanks&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">UFO</dc:creator><pubDate>Sun, 04 Dec 2022 17:45:27 -0000</pubDate><guid>https://sourceforge.netb82692df230513ef692bced34def54ba6f3c6f69</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#7193/0f90</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'd still like to thank you: you did spend some time/effort on this, and pointed me to a nice starting point for me to work on. &lt;br/&gt;
The whatsnew would say "thanks github.org/ufo for help" -- unless you object (or prefer an alternate credit such as name or email).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Sun, 04 Dec 2022 10:35:45 -0000</pubDate><guid>https://sourceforge.netf7758436a0df6d4c0bc0a5589ed25d707bcc75dd</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#7193</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Horea,&lt;br/&gt;
thanks a lot, but no need to credit me! I've seen some other forks of your project on Github in the past and just gathered some Python 3 port patches from here and there. In the end I didn't have to add a lot (of quick and dirty hacks) to make it really work for me. Then I just created a branch to make it easier for you to diff, because the other forks on Github always added a lot of additional strange features, so it was kinda cumbersome to see the naked Python 3 port. I see you already correctly cleaned up the port, so thanks for your work again. Looking forward to see your project on Github. I'm sure there will be others too contributing to it. I also tried patching it that it could be simultaneously be packed as a Windows-only .whl file, so that it could be uploaded on pypi.org and installed via 'pip'. Besides still being freezed as an exe. But I failed bringing both package structure types together. Maybe I'll soon give it another try, since I'm sure I'll still be using PyCmd in the future. I have a look at other tools (new MS Terminal, cmder, ConEmu) sometimes, but they will all keep missing the unix-like feeling/features that you add(ed) for PyCmd. Please keep it up!&lt;br/&gt;
Best regards&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">UFO</dc:creator><pubDate>Sat, 03 Dec 2022 20:31:41 -0000</pubDate><guid>https://sourceforge.net7580a0a351abe63258592c8f07cd7fa1d1623582</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#60da/bc11</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The patch did not apply directly (I had some unpushed commits on my local branch -- my bad) so I sort of went through your changes and applied them manually, with some small adjustments here and there; you can see the result on branch "py3" in the SF repo. &lt;/p&gt;
&lt;p&gt;Among the adjustments I would note: &lt;br/&gt;
1. dropped support for Py2: I expect most users' init.py files are Py3-compatible, or at least can be ported trivially&lt;br/&gt;
2. simplified the console.py port&lt;br/&gt;
3. fixed the setting of the window title (via SetConsoleTitleA)&lt;/p&gt;
&lt;p&gt;Now I would like to merge this work into the master branch and credit you (1) in the commit description and (2) in the NEWS.txt where the porting to Py3 will be announced. If you agree to this plan, please let me know how you want to be credited (name and/or email and/or github account).&lt;/p&gt;
&lt;p&gt;Note that the cx_freeze script and the Makefile are yet to be ported; also Py3 should bring improved support for non-ASCII/non-codepage paths, which PyCmd should now be able to finally handle properly.&lt;/p&gt;
&lt;p&gt;Once again, thank you for your contribution -- it really helps the project. I hope that we can cooperate further (and smoother!) after I relocate the project to github and get access to more modern collaboration methods (e.g. pull requests).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Fri, 02 Dec 2022 21:53:06 -0000</pubDate><guid>https://sourceforge.net5abf1d6951bf0775431c3b610fea2c56f3d04bdc</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#60da/140e</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I had a quick look and this looks very nice (and quite helpful) -- thank you very much!&lt;br/&gt;
I was actually planning to work on the Py3 porting during the next few days as I have some spare time; so your contribution comes at the perfect time :) I will review the diff and come back to you to discuss about integrating the changes.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Wed, 30 Nov 2022 22:40:46 -0000</pubDate><guid>https://sourceforge.netbae388861d62db510980a615a7aa01f362c30f23</guid></item><item><title>#26 Move to Python 3 (and potentially to github)</title><link>https://sourceforge.net/p/pycmd/feature-requests/26/?limit=25#60da</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Horea,&lt;br/&gt;
yes, you should really move your great project to Github.&lt;br/&gt;
Regarding Python 3: I've pushed a branch today which is compatible with Python 2 and Python 3, since I've needed it to be compatible with both versions in a personal project. I've tested it with Python 3.10 and Python 2.7.&lt;br/&gt;
The branch is directly based on the source that you uploaded 2 weeks ago: &lt;a href="https://github.com/ufo/PyCmd/tree/raw_fork_from_sourceforge_py3_compatible" rel="nofollow"&gt;https://github.com/ufo/PyCmd/tree/raw_fork_from_sourceforge_py3_compatible&lt;/a&gt; . So you could simply take a look at the diff and maybe merge it into your project.&lt;br/&gt;
Best regards&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">UFO</dc:creator><pubDate>Wed, 30 Nov 2022 20:01:37 -0000</pubDate><guid>https://sourceforge.net38b3e1a197440a840eb66b5c5c9bd87a726b3202</guid></item><item><title>#3 option for tab to complete without showing options</title><link>https://sourceforge.net/p/pycmd/feature-requests/3/?limit=25#db1a</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If the reason for this request is to avoid "polluting" the screen, the new "zsh" completion mode (should be on by default for a recent PyCmd, unless behavior.completion_mode is set it the init.py) helps: the list of completions is erased from the screen when no longer needed.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Sun, 13 Nov 2022 23:02:05 -0000</pubDate><guid>https://sourceforge.net88ad380303943a7a796fccfcda425b6f5b9122fb</guid></item><item><title>#21 Tab cycling like in cmd.exe</title><link>https://sourceforge.net/p/pycmd/feature-requests/21/?limit=25#0d1f/4547</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;A small note here: the updated "zsh-style" completion mechanism which supports navigating the list (which btw is now default unless overridden by behavior.completion_mode in init.py) shares one more advantage with the "cyclic" mode: less garbage is left over on the screen (the list of completions is erased when no longer needed)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horea Haitonic</dc:creator><pubDate>Sun, 13 Nov 2022 22:58:29 -0000</pubDate><guid>https://sourceforge.netf64494e79495ee606ea5d6004b6785ea04295c23</guid></item></channel></rss>