FWIW, setting something to #f in Emacs Lisp means you’re setting it to TRUE, not FALSE. Elisp is not Scheme.

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

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.

Try commenting out the definition of dired-jump in dired+.el, and see if that makes a difference. (The main difference is that the Dired+ version opens the directory listing with the destination, it it’s hidden.)

Then M-x diredp-send-bug-report. Provide your Emacs release, platform etc. info, and preferably a recipe starting from emacs -Q. Thx.

Maybe check also with the pdf-tools maintainer.

Learn to Ask Emacs. Use the Help menu in the menu-bar - get to know it well. Learn the help commands on prefix key C-h, including C-h r, which takes you to the Emacs manual, and C-h S, which looks up a symbol (word) in that manual.

Learn how to create and use keyboard macros. Over time, learn some Elisp, which is the golden key to asking Emacs.

Just an observation.

In the responses to the question here, there is close to zero actual comparison of Doom and Spacemacs features or behavior, or mention of specific benefits of one or the other.

Most of the response content is essentially voting - rooting for the colors of one team or the other. Maybe OP finds that that helps somehow; maybe not. (If it does, what a pity.)

Dunno what this indicates. Maybe it says something about Reddit, or about the nature of such questions, or about Doom and Spacemacs fans?

I really don’t know. Just a weightless observation. And maybe after I write this it’ll (hopefully) be proven wrong.

Just an observation.

In the responses to the question here, there is close to zero actual comparison of Doom and Spacemacs features or behavior, or mention of specific benefits of one or the other.

Most of the response content is essentially voting - rooting for the colors of one team or the other. Maybe OP finds that that helps somehow; maybe not. (If it does, what a pity.)

Dunno what this indicates. Maybe it says something about Reddit, or about the nature of such questions, or about Doom and Spacemacs fans?

I really don’t know. Just a weightless observation. And maybe after I write this it’ll (hopefully) be proven wrong.

At first I thought this was going to be about the very useful and delightful topic of “Best practices for avoiding work.”

My inner Maynard G. Krebs jumped up to say “Work?!”.

Here are some ways to move around. The first two are in vanilla Emacs. (There are previous functions corresponding to the next functions mentioned.)

• C-M-e and C-M-a: Move to next “defun” (function definition).

• Imenu, if you know the name of the thing (e.g. a definition) you`re looking for. (Various libraries let you complete/filter and cycle among candidates.)

• next-visible-thing. Moves to end of next THING. First nonconsecutive use prompts for THING type. Or use next-visible-thing to define such a command for a specific kind of THING (so no prompt needed for the kind).

  Requires library thing-cmds.el, which requires hide-comnt.el.

  Predefined THINGS (library thingatpt+.el needed for some):

  sexp, button, char, char-same-line, color, comment, decimal-number, defun, email, filename, hex-number, line, list, list-contents, non-nil-symbol-name, number, overlay, page, paragraph, region-or-word, sentence, string, string-contents, symbol, symbol-name, unquoted-list, url, whitespace, whitespace-&-newlines, word

  “Visible” means invisible text is skipped. Option ignore-comments-flag controls whether to also ignore text in comments.

• Command fw-to-next-thing. Moves to the start of the next THING (unlike next-visible-thing, which moves to its end).

  Requires libraries find-where.el and thingatpt+.el needed for some).

  Library find-where.el lets you get something at a position where an arbitrary predicate is true (not just a position at the start of a text THING), or move to such a position.

  E.g., function fw-next-thing returns the next THING and its position, and command fw-to-next-thing goes there.

  E.g., this defines a command to move to the beginning of the next sexp:

    (defun to-next-sexp (n)
      "Go to next start of a sexp."
      (interactive "p")
      (fw-to-next-thing 'sexp nil n))
  

  Likewise, for fw-next-where and fw-to-next-where, which look for the next place and some data where some predicate is satisfied.

  See the Commentary in find-where.el.

• Commands in library isearch-prop.el to search within the text of certain things.

  E.g., isearchp-imenu-non-interactive-function searches only within (or only outside of) definitions of functions that are not commands. isearch-property-forward searches only within text that has (or doesn’t have) a given text or overlay property. isearchp-zones-forward searches only within (or only outside) the text of a given set of zones (i.e., within a noncontiguous region).

• The old library hideif.el lets you hide text that’s within ifdefs.

https://www.emacswiki.org/emacs/download/thing-cmds.el

https://www.emacswiki.org/emacs/download/hide-comnt.el

https://www.emacswiki.org/emacs/download/find-where.el

https://www.emacswiki.org/emacs/download/thingatpt%2B.el

https://www.emacswiki.org/emacs/download/isearch-prop.el