[Discuss] Things in Hidden, Magic . Files

[smallm at sdf.org (Mike Small)]

Did you do an apt purge? I wouldn't think emacs package source files
would be considered configuration but who knows.

As an aside, with emacs packages I'd be inclined not to use the distro
repo. It's unlikely you'd have a distro package that depends on an elisp
package outside of emacs's guts, so using emacs's native package manager
won't cause you the trouble using Perl's or Python's might (without some
wrapper thing insulating you from the distro). IMO the native
interpreter/language packager would always be better to use and distros
should stay out of it, except for that pesky problem that distro
software might also need some version of the modules you use.

What about using emacs's own symbolic debugger to step through the elpy
elisp code until things get weird? It's pretty easy to get started
with. Only a handful of key presses to learn until you can do the basics
with it.

The emacs manual section "The Init File, `~/.emacs'" describes what
emacs loads on start up. The load-path variable shows the places elisp
files can come from (or most of the places? maybe some of the init files
or package manager stuff isn't in that list). That section also shows how
to start emacs without loading the usual init files. You could try that
and manually load the things you need for a basic Python debugging
session. Then if that works rebuild the death star from the inside out
until the weirdness reasserts.

Kent Borg <kentborg at borg.org> writes:

> Short version: Where are all the places to put things to change
> emacs's behavior?
>
> Longer version: I am an emacs person, programming in Python mostly
> these days. So the other day I thought I should get modern (always a
> risk) and get emacs to do clever tab-completion and stuff. I tried
> installing elpy.
>
> It has its advantages, it has its drawbacks, but then I stumbled on a
> *big* problem: source code debugging with pdb quit working. Emacs used
> to open another pane and put an arrow next to the line about to be
> executed. No longer. Naturally I suspect elpy.
>
> So I did my best to uninstall it. And uninstall the apt-get stuff I
> installed to make elpy happy.
>
> My source code debugging is still not fixed.
>
> I try debugging as another user and that does work. I try hiding my
> .emacs file and .emacs.d directory in another directory, and it is
> still not working.
>
> Running Debian 9.
>
> Ideas?
>
> Thanks,
>
> -kb
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>

-- 
Mike Small
smallm at sdf.org