00-11

Learn Emacs Lisp on Emacs Wiki.

Do you see the problem when you start Emacs with emacs -Q?

Check your value of option default-frame-alist...

Is there a easy way to use emacs ?

Yes. Start it and type C-h t. Follow the simple tutorial directions.

https://emacs.stackexchange.com/q/79303/105

A couple of the Isearch+ features that let you limit the search space/context.

1. You can limit isearching to the text in the region. Controlled by a user option, and can be toggled with C-x n during Isearch. Works also for a noncontiguous region, such as a rectangle.

2. You can switch any time to isearching outside, instead of inside, the region.

3. You can search within/without the zones of text defined by the lazy-highlight matches of a previous search.

Or search within/without the zones of text that have a certain text property or set of properties (optionally considering their values) -- any properties.

4. Dynamic Isearch filtering: add/remove any number of search filters while isearching.

• Isearch+

• Dynamic Isearch Filtering

+1.

• +1 for the Abelson & Sussman lecture(s).

• Plus links at Emacs Wiki Learn Emacs Lisp

As I said, please follow up off list, using M-x diredp-send-bug-report. You haven't even mentioned your platform etc.

One quick thing to try would be to evaluate this, to see if the extra font-locking is the problem: (remove-hook 'dired-mode-hook 'diredp--set-up-font-locking).

Keep investigating. (I assume the problem doesn't arise with just Helm and PDF-tools (i.e., without Dired+).)

d in the debugger steps into evaluating the current sexp to be evaluated.

c steps past it, i.e., it evaluates it without digging into the steps of evaluating it.

So you can use c to skip over steps that you don't want to get into in to detail, and use d otherwise.

So the problem is apparently not with Dired+'s dired-jump, but something else in Dired+. But if you can repro the problem easily using dired-jump, maybe try M-x debug-on-entry dired-jump and step through the debugger to see what seems to be the problem - with emacs -Q and just Dired+ and PDF-tools loaded. But instead of trying to debug it here, M-x diredp-send-bug-report, as mentioned above.

Bisect your init file. You can use command comment-region comment out 1/2 of it, then 3/4, then 7/8,... till you can see easily what's causing the problem. This is a binary search, so it narrows things down quickly.

Do you see the same problem if you start Emacs using emacs -Q (no init file)? If not, bisect your init file to find the culprit.