Hi.

Here is the log from an IRC log from yesterday:

[16:55] <rbrito> Hi there.
[16:56] <rbrito> Before I file a bug against autojump, I would like to
see if other people are seeing the same problem that I am.
[16:58] <rbrito> I'm using bash and I followed the instructions
included in /usr/share/doc/autojump/README.Debian
[16:59] <rbrito> I have also searched a lot with google and it seems
that the problem is also present in Ubuntu.
[17:00] <rbrito> The issue is that when I use autojump, the database
of directories doesn't get updated when I enter new directories.
[17:00] <rbrito> Is there anyone else seeing this behavior?
[17:02] <rbrito> The only cases where I see new directories getting
included in the database of past directories are when I manually force
autojump to include a given directory with "j -a ." or if I
immediately source the configuration file with: "source
/usr/share/autojump/autojump.bash"
[17:03] <rbrito> This was noticeable on a new machine, since the
database is, of course, empty upon installation...
[17:05] <rbrito> But now that I think more about this, I may have seen
this issue on my other computers, with the priorities of directories
not being updated, but, in this case, the databases were not empty, so
I didn't notice right away...
[17:57] <annadane> i mean, i'd say just submit the bug report
[17:57] <annadane> rbrito
[17:57] <rbrito> annadane: Thanks for the recommendation.
[17:58] <annadane> it can't hurt
[17:58] <rbrito> annadane: do you see the problem also (if you use it?)
[17:58] <annadane> i don't use it
[17:58] <rbrito> OK, no problems.
[17:58] <rbrito> Thanks.

The problem is that I have not changed anything in my configuration in
years (since, say, I contributed a patch to
https://bugs.debian.org/705516 or
https://github.com/wting/autojump/commit/2a49b8ca475701a65cfb55324a765faf8eb5265d)
and I just move such configuration from machine to machine (my
dotfiles are in a git repo), but now I don't see the database of past
directories ever get updated.


Thanks for packaging autojump BTW,

reassign 859245 libvte-2.91-common
thanks

The problem that I reported in bug 859245 has occured because the
instructions in

    /usr/share/doc/libvte-2.91-0/README.Debian

clobber the contents of what autojump also needs (PROMPT_COMMAND variable),
which, unfortunately, was my case, since I had:

1 - first, set up autojump in my bash_profile
2 - right after autojump, vte set up as per the instructions in the
    README.Debian above

Switching the order of the assignments above is a workaround that make
things work, but clobbering/overwriting configurations/variables of the
users (when they want a cumulative behavior) is definitely wrong.

    To Tanguy (maintainer of autojump): You probably may want to add a note
    in autojump's instructions (possibly notifying upstream, if this isn't
    documented already) to avoid giving users some headaches.


(Another related bug that I just noticed when gathering information for this
report: /usr/share/doc/libvte-2.91-0/README.Debian should be updated to
point to /etc/profile.d/vte-2.91.sh instead of only /etc/profile.d/vte.sh).


Thanks,

Rogério Brito.