Re: [Python-mode] huge files
On Wed, Feb 15, 2012 at 07:57:46AM -0500, Barry Warsaw wrote: On Feb 15, 2012, at 09:34 AM, Andreas Röhler wrote: think it's basically historical. People interested in developing/understanding might check out and use the components branch https://code.launchpad.net/~a-roehler/python-mode/components-python-mode I'm doing all my developing and Python editing there. It's sometimes ahead several days, if new features are introduced. But the same tests are run before commits, so a possible loss in stability is mince. BTW in future we could create a declared stable branch of components and make two tarballs for release. I've always thought that because python-mode.el is a separate download, it's better to have one big file. This makes it easier for users to add it to their Emacsen, even though it makes it more difficult to maintain, as rightly observed. But maybe we're at the tipping point where that trade-off should go the other way. Good, discoverable, installation documentation would go a long way toward alleviating those concerns. I run python-mode out of the bzr trunk, so I'm probably not a good use case. In a very real sense, this is Andreas's decision now. He who does the work, decides and Andreas has for quite a while now assumed primary ownership on the code, by virtue of his great work on the mode. I have no place to stand in the way of his decision on this. Extending what Barry said ... python-mode.el already has a hurdle to overcome, as it's not distributed with emacs. I think a single file makes it easier for non-experts (I'm in this category) to drop in .emacs.d and run. http://marmalade-repo.org/about However, as the Marmalade server (hopefully) becomes a standard method for distributing 3rd party emacs packages, then multi-file python-mode will be a non-issue. Perhaps we might see some convergence in this direction? Agreed that the decision is Andreas's, and I thank him for his efforts. Jeff Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] making stack traces clickable in gud.el pdb output.
François, Hah! So funny for you to bring up *that* specific post from Barry. It's been sitting in my inbox as msg #1 for the past couple years. Even though I copied it to my org notes, I've always had it there. So when your email arrived, my reader threaded it back to Barry's 2-year-old post. What!? Then I read your text and it all made sense. ;-) P.S. to Barry: My upgrade to Emacs 24 via launchpad has been a totally painless non-event. Jeff Shawn White Bauer Rubicon, Inc. On Thu, Jan 26, 2012 at 10:44:05PM -0500, François Pinard wrote: Barry Warsaw ba...@python.org writes: How do I invoke pdbtrack from python-mode? It's really easy. You still insert 'import pdb; pdb.set_trace()' at the spot in your code where you want to break. Then run your code from a shell buffer. When you hit the break point, you'll drop into pdb. pdb-track will notice the new prompt and you'll be able to interact with it right there. You'll use pdb commands but you'll get the nice two-screen view with code tracking. Hi, python-mode people. I quote Barry's explanation above, as an example of fruitful instructions about how to use python-mode. Looking at the mailing list archives, here and there, I read other nice advice or tricks. But it's a pity that these did not get collected into a user documentation. So my suggestions: * take the above quote and drop it *as is* within the README file (yes, the README, not in the doc/ directory, nor any fancier place). Right now, without hesitation. * whenever any usage advice is given on the list, someone with commit powers immediately copies it, as is, within the README. * do not try to devise a fancy structure or flowing text right away, the emergency right now is to give some informational meat to users, rather than a nice structure filled with lots of TBDs (to be done). The TBDs should go to the TODO file (which, by the way, is the traditional capitalisation for it), not in the README. * do not worry, structure will come very naturally, later, as material accumulates within README. Information first, structure later. * integrate the INSTALL file within README, get rid of it as a separate file. It is not worth a file as it stands right now. Let it grow within README, and give it an existence in a separate file only when it will hold enough substance to be worth its own file. Do not think INSTALL exists so people may start without having to read README. On the contrary, manage so users will more likely peruse README. * get rid of doc/, or at least change its name. Users are mislead to think there is a documentation in there that is usable for them. François P.S. Reading further, Barry wrote: I owe Ken Manheimer a lifetime supply of [insert beverage] for this beautiful hack. Sigh! If only I could have developed something so attractive that Barry did such an offer to *me*. I spoiled my life! :-) ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] Python Developers Emacs Environment - PDEE
On Wed, Nov 09, 2011 at 05:45:24PM +0100, Andreas Röhler wrote: Am 09.11.2011 14:56, schrieb Jeff Bauer: Would it make sense for PDEE to be delivered through Marmalade? http://marmalade-repo.org/ I'm kind of excited that emacs will soon have a standard package manager. Jeff Bauer Rubicon, Inc. Hi Jeff, as it's around establishing a workflow for the project still, you could make us the pleasure opening an issue at https://github.com/pdee/pdee thanks pointing at the matter, Andreas Submitted to the github project, issue #1. -Jeff ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] emacs
Rinu, Just follow the instructions in python-mode.el: To install, just drop this file into a directory on your load-path and byte-compile it. To set up Emacs to automatically edit files ending in .py using python-mode, add to your emacs init file (~/.emacs, ~/.emacs.el, or ~/.emacs.d/init.el) the following code: (setq auto-mode-alist (cons '(\\.py$ . python-mode) auto-mode-alist)) (setq interpreter-mode-alist (cons '(python . python-mode) interpreter-mode-alist)) (autoload 'python-mode python-mode Python editing mode. t) Alternatively, if you want an out-of-the box emacs python experience, you can try: http://gabrielelanaro.github.com/emacs-for-python/ But it's using a home brew python.el version rather than python-mode.el: https://github.com/fgallina/python.el Jeff Bauer Rubicon, Inc. On Fri, Oct 28, 2011 at 07:55:51AM +0530, Rinu Boney wrote: I Would Love to Know How To Set Up Emacs As A Python Code Editing Environment Using python-mode.el. I Have No Experience in Emacs. Can U Help or Point Out Something That Can Help Me ? Thanks. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] py-python-command default
On Wed, Sep 28, 2011 at 12:04:15PM -0400, Barry Warsaw wrote: On Sep 28, 2011, at 01:15 PM, David Miller wrote: Yes, please. :) ipython is a separate program that doesn't come with stock Python. How about conditionally setting it - this is essentially what Django does with it's shell (defcustom py-python-command (if (executable-find ipython) ipython python) I'm not entirely in favor of this. While I have ipython installed, I still want to use regular 'ol python in my Emacs. Of course, should you make this change I can always customize the variable. OTOH, I don't want to stand in the way of what's really convenient for folks. So I guess I'm -0. Georg, what do you think? -Barry Agreed. Django originally had this behavior. I filed a patch to fix the implicit assumption. Vanilla python should be the default, ipython (or whatever) when specifically requested. Jeff Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] Hello
On 03/02/2010 05:12 PM, Georg Brandl wrote: I've only just subscribed this list since I complained a bit to Barry about the general state of Python in Emacs and he managed to recruit me as a contributor :) Hi Georg! Any cool Python/Emacs tricks you'd care to share? (Or Barry?) Jeff Shaun White Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] coding in emacs 23
On 01/27/2010 03:09 AM, Bernhard Herzog wrote: On 27.01.2010, Jeff Bauer wrote: It used to be if my cursor was positioned on (0,1) and I pressed ^N, the cursor would jump down to the second line of code (0,3). Now it goes to (0,2) which is still considered (0,50). That's a new default in Emacs 23 called visual line mode IIRC. You can get the old behavior back with the following setting in ~/.emacs: (setq line-move-visual nil) I see: http://www.emacswiki.org/emacs/VisualLineMode As the wiki suggests, it would make more sense to enable this for text mode and leave it disabled for editing code: (add-hook 'text-mode-hook 'turn-on-visual-line-mode) -Jeff ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
[Python-mode] coding in emacs 23
After upgrading to emac23, I noticed one big difference in editing python code ... or, well editing anything. 0123456789012345678901234567890123456789 1 One-really-long-line-of-text-and-newline 2 -doesn't-appear-until-full-stop-HERE. 3 Second-line-of-code It used to be if my cursor was positioned on (0,1) and I pressed ^N, the cursor would jump down to the second line of code (0,3). Now it goes to (0,2) which is still considered (0,50). I think I preferred the older behavior for coding -- especially when I'm ThinkingInPython. Now I grab a line of code only to look up and realize I've only grabbed the first portion of the python statement. This also messes up the way I used to do some on-the-fly macros. Anyone else affected by this disconnect? -- Jeff Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] making stack traces clickable in gud.el pdb output.
clickable? Is that like using that mouse thing? To paraphrase a wise man, There's no clicking in Emacs! :) But the track ball scroll wheel is AWESOME. I've never tried running pdb from an emacs shell. Thanks for the tip! Jeff Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] merging python-mode.el and python.el
Barry Warsaw wrote: I also think that python-mode.el feels more natural to Python programmers, but I have only anecdotal evidence for that. Just last week I had a colleague ask me why Emacs wasn't working the way he wanted while editing his Python code. I made a wild guess and pointed him to python-mode.el and it solved his problem. That's happened to me several times when Emacs users don't realize that they have a different Python mode. Yes, I was one of those who wondered why Python didn't feel right in Emacs until I realized there were multiple versions. It's a subjective thing, but no less important for that. I still propose we GPLv3 python-mode.el. Thus if we cannot merge, we will simply continue to develop python-mode.el separately, educate users as to the differences, and let them decide which they prefer. With a GPLv3 python-mode.el we can all borrow from each other. +1 Jeff Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] paren-deactivate
s...@pobox.com wrote: My preference would be to leave it as-is. +1. While not up to lisp-y levels, I also find it useful with nested tuples/functions, esp. if they span multiple lines. -Jeff ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] merging
Beverley, If you're taking requests, support for which-func-mode might be on my list for the python-mode.el merge. Thanks. Jeff Bauer Rubicon, Inc. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] underscore syntax
Diez B. Roggisch wrote: Jeff Bauer schrieb: Did the behavior python-mode change with respect to the syntax of vars_with_underscores? Keying M-f or M-b now stops the cursor at the underscores rather than grabbing the entire variable. Prior, in GNU Emacs 21.4, the behavior worked as I expected. I don't think that's a python-mode issue - rather emacs behaves differently. Dunno how to change that though. My emacs doesn't stop at underscores. Regardless of python-mode-age. I was running the standard python-mode that ships with Ubuntu 8.10 when I noticed it stopped at underscores. Downloading the recently announced python-mode.el 5.0.0 from LaunchPad (Thanks, Barry!) fixed this behavior, though I'm sure it had more to do with switching away from whatever python-mode is being shipped in the current Ubuntu. All is now sweetness and light. -Jeff ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
