[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-8091":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":19,"rankGlobal":10,"rankLanguage":10,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":23,"hasPages":21,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":25,"readmeContent":26,"aiSummary":27,"trendingCount":16,"starSnapshotCount":16,"syncStatus":28,"lastSyncTime":29,"discoverSource":30},8091,"listen","guard\u002Flisten","guard","The Listen gem listens to file modifications and notifies you about the changes.","https:\u002F\u002Frubygems.org\u002Fgems\u002Flisten",null,"Ruby",1964,250,49,23,0,1,14,57.1,"MIT License",false,"master",true,[],"2026-06-12 04:00:37","# Listen\n\nThe `listen` gem listens to file modifications and notifies you about the changes.\n\n[![Development Status](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fworkflows\u002FDevelopment\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Factions?workflow=Development)\n[![Gem Version](https:\u002F\u002Fbadge.fury.io\u002Frb\u002Flisten.svg)](http:\u002F\u002Fbadge.fury.io\u002Frb\u002Flisten)\n[![Code Climate](https:\u002F\u002Fcodeclimate.com\u002Fgithub\u002Fguard\u002Flisten.svg)](https:\u002F\u002Fcodeclimate.com\u002Fgithub\u002Fguard\u002Flisten)\n[![Coverage Status](https:\u002F\u002Fcoveralls.io\u002Frepos\u002Fguard\u002Flisten\u002Fbadge.svg?branch=master)](https:\u002F\u002Fcoveralls.io\u002Fr\u002Fguard\u002Flisten)\n\n## Features\n\n* OS-optimized adapters on MRI for Mac OS X 10.6+, Linux, \\*BSD and Windows, [more info](#listen-adapters) below.\n* Detects file modification, addition and removal.\n* You can watch multiple directories.\n* Regexp-patterns for ignoring paths for more accuracy and speed\n* Increased change detection accuracy on OS X HFS and VFAT volumes.\n* Continuous Integration: tested on selected Ruby environments via [Github Workflows](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Ftree\u002Fmaster\u002F.github\u002Fworkflows).\n\n## Issues \u002F limitations\n\n* Limited support for symlinked directories ([#279](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F279)):\n  * Symlinks are always followed ([#25](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F25)).\n  * Symlinked directories pointing within a watched directory are not supported ([#273](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fpull\u002F273).\n* No directory\u002Fadapter-specific configuration options.\n* Support for plugins planned for future.\n* TCP functionality was removed in `listen` [3.0.0](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Freleases\u002Ftag\u002Fv3.0.0) ([#319](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F319), [#218](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F218)). There are plans to extract this feature to separate gems ([#258](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F258)), until this is finished, you can use by locking the `listen` gem to version `'~> 2.10'`.\n* Some filesystems won't work without polling (VM\u002FVagrant Shared folders, NFS, Samba, sshfs, etc.).\n* Windows and \\*BSD adapter aren't continuously and automatically tested.\n* OSX adapter has some performance limitations ([#342](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F342)).\n* Listeners do not notify across forked processes, if you wish for multiple processes to receive change notifications you must [listen inside of each process](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F398#issuecomment-223957952).\n\nPull requests or help is very welcome for these.\n\n## Install\n\nThe simplest way to install `listen` is to use [Bundler](http:\u002F\u002Fbundler.io).\n\n```ruby\ngem 'listen'\n```\n\n## Complete Example\nHere is a complete example of using the `listen` gem:\n```ruby\nrequire 'listen'\n\nlistener = Listen.to('\u002Fsrv\u002Fapp') do |modified, added, removed|\n  puts(modified: modified, added: added, removed: removed)\nend\nlistener.start\nsleep\n```\nRunning the above in the background, you can see the callback block being called in response to each command:\n```\n$ cd \u002Fsrv\u002Fapp\n$ touch a.txt\n{:modified=>[], :added=>[\"\u002Fsrv\u002Fapp\u002Fa.txt\"], :removed=>[]}\n\n$ echo more >> a.txt\n{:modified=>[\"\u002Fsrv\u002Fapp\u002Fa.txt\"], :added=>[], :removed=>[]}\n\n$ mv a.txt b.txt\n{:modified=>[], :added=>[\"\u002Fsrv\u002Fapp\u002Fb.txt\"], :removed=>[\"\u002Fsrv\u002Fapp\u002Fa.txt\"]}\n\n$ vi b.txt\n# add a line to this new file and press ZZ to save and exit\n{:modified=>[\"\u002Fsrv\u002Fapp\u002Fb.txt\"], :added=>[], :removed=>[]}\n\n$ vi c.txt\n# add a line and press ZZ to save and exit\n{:modified=>[], :added=>[\"\u002Fsrv\u002Fapp\u002Fc.txt\"], :removed=>[]}\n\n$ rm b.txt c.txt\n{:modified=>[], :added=>[], :removed=>[\"\u002Fsrv\u002Fapp\u002Fb.txt\", \"\u002Fsrv\u002Fapp\u002Fc.txt\"]}\n```\n\n## Usage\n\nCall `Listen.to` with one or more directories and the \"changes\" callback passed as a block.\n\n``` ruby\nlistener = Listen.to('dir\u002Fto\u002Flisten', 'dir\u002Fto\u002Flisten2') do |modified, added, removed|\n  puts \"modified absolute path array: #{modified}\"\n  puts \"added absolute path array: #{added}\"\n  puts \"removed absolute path array: #{removed}\"\nend\nlistener.start # starts a listener thread--does not block\n\n# do whatever you want here...just don't exit the process :)\n\nsleep\n```\n## Changes Callback\n\nChanges to the listened-to directories are reported by the listener thread in a callback.\nThe callback receives **three** array parameters: `modified`, `added` and `removed`, in that order.\nEach of these three is always an array with 0 or more entries.\nEach array entry is an absolute path.\n\n### Pause \u002F start \u002F stop\n\nListeners can also be easily paused and later un-paused with start:\n\n``` ruby\nlistener = Listen.to('dir\u002Fpath\u002Fto\u002Flisten') { |modified, added, removed| puts 'handle changes here...' }\n\nlistener.start\nlistener.paused?     # => false\nlistener.processing? # => true\n\nlistener.pause       # stops processing changes (but keeps on collecting them)\nlistener.paused?     # => true\nlistener.processing? # => false\n\nlistener.start       # resumes processing changes\nlistener.stop        # stop both listening to changes and processing them\n```\n\n  Note: While paused, `listen` keeps on collecting changes in the background - to clear them, call `stop`.\n\n  Note: You should keep track of all started listeners and `stop` them properly on finish.\n\n### Ignore \u002F ignore!\n\n`Listen` ignores some directories and extensions by default (See DEFAULT_IGNORED_FILES and DEFAULT_IGNORED_EXTENSIONS in Listen::Silencer).\nYou can add ignoring patterns with the `ignore` option\u002Fmethod or overwrite default with `ignore!` option\u002Fmethod.\n\n``` ruby\nlistener = Listen.to('dir\u002Fpath\u002Fto\u002Flisten', ignore: \u002F\\.txt\u002F) { |modified, added, removed| # ... }\nlistener.start\nlistener.ignore! \u002F\\.pkg\u002F # overwrite all patterns and only ignore pkg extension.\nlistener.ignore \u002F\\.rb\u002F   # ignore rb extension in addition of pkg.\nsleep\n```\n\nNote: `:ignore` regexp patterns are evaluated against relative paths.\n\nNote: Ignoring paths does not improve performance, except when Polling ([#274](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fissues\u002F274)).\n\n### Only\n\n`Listen` watches all files (less the ignored ones) by default. If you want to only listen to a specific type of file (i.e., just `.rb` extension), you should use the `only` option\u002Fmethod.\n\n``` ruby\nlistener = Listen.to('dir\u002Fpath\u002Fto\u002Flisten', only: \u002F\\.rb$\u002F) { |modified, added, removed| # ... }\nlistener.start\nlistener.only \u002F_spec\\.rb$\u002F # overwrite all existing only patterns.\nsleep\n```\n\nNote: `:only` regexp patterns are evaluated only against relative **file** paths.\n\n\n## Options\n\nAll the following options can be set through the `Listen.to` after the directory path(s) params.\n\n``` ruby\nignore: [%r{\u002Ffoo\u002Fbar}, \u002F\\.pid$\u002F, \u002F\\.coffee$\u002F]   # Ignore a list of paths\n                                                # default: See DEFAULT_IGNORED_FILES and DEFAULT_IGNORED_EXTENSIONS in Listen::Silencer\n\nignore!: %r{\u002Ffoo\u002Fbar}                           # Same as ignore options, but overwrite default ignored paths.\n\nonly: %r{.rb$}                                  # Only listen to specific files\n                                                # default: none\n\nlatency: 0.5                                    # Set the delay (**in seconds**) between checking for changes\n                                                # default: 0.25 sec (1.0 sec for polling)\n\nwait_for_delay: 4                               # Set the delay (**in seconds**) between calls to the callback when changes exist\n                                                # default: 0.10 sec\n\nforce_polling: true                             # Force the use of the polling adapter\n                                                # default: none\n\nrelative: false                                 # Whether changes should be relative to current dir or not\n                                                # default: false\n\npolling_fallback_message: 'custom message'      # Set a custom polling fallback message (or disable it with false)\n                                                # default: \"Listen will be polling for changes. Learn more at https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten#listen-adapters.\"\n```\n\n## Logging and Debugging\n\n`Listen` logs its activity to `Listen.logger`.\nThis is the primary method of debugging.\n\n### Custom Logger\nYou can call `Listen.logger =` to set a custom `listen` logger for the process. For example:\n``` ruby\nListen.logger = Rails.logger\n```\n\n### Default Logger\nIf no custom logger is set, a default `listen` logger which logs to to `STDERR` will be created and assigned to `Listen.logger`.\n\nThe default logger defaults to the `error` logging level (severity).\nYou can override the logging level by setting the environment variable `LISTEN_GEM_DEBUGGING=\u003Clevel>`.\nFor `\u003Clevel>`, all standard `::Logger` levels are supported, with any mix of upper-\u002Flower-case:\n``` ruby\nexport LISTEN_GEM_DEBUGGING=debug # or 2 [deprecated]\nexport LISTEN_GEM_DEBUGGING=info  # or 1 or true or yes [deprecated]\nexport LISTEN_GEM_DEBUGGING=warn\nexport LISTEN_GEM_DEBUGGING=fatal\nexport LISTEN_GEM_DEBUGGING=error\n```\nThe default of `error` will be used if an unsupported value is set.\n\nNote: The alternate values `1`, `2`, `true` and `yes` shown above are deprecated and will be removed from `listen` v4.0.\n\n### Disabling Logging\nIf you want to disable `listen` logging, set\n``` ruby\nListen.logger = ::Logger.new('\u002Fdev\u002Fnull')\n```\n\n### Adapter Warnings\nIf listen is having trouble with the underlying adapter, it will display warnings with `Kernel#warn` by default,\nwhich in turn writes to STDERR.\nSometimes this is not desirable, for example in an environment where STDERR is ignored.\nFor these reasons, the behavior can be configured using `Listen.adapter_warn_behavior =`:\n``` ruby\nListen.adapter_warn_behavior = :warn   # default (true means the same)\nListen.adapter_warn_behavior = :log    # send to logger.warn\nListen.adapter_warn_behavior = :silent # suppress all adapter warnings (nil or false mean the same)\n```\nAlso there are some cases where specific warnings are not helpful.\nFor example, if you are using the polling adapter--and expect to--you can suppress the warning about it\nby providing a callable object like a lambda or proc that determines the behavior based on the `message`:\n``` ruby\nListen.adapter_warn_behavior = ->(message) do\n  case message\n  when \u002FListen will be polling for changes\u002F\n    :silent\n  when \u002Fdirectory is already being watched\u002F\n    :log\n  else\n    :warn\n  end\nend\n```\nIn cases where the `Listen` gem is embedded inside another service--such as `guard`--the above configuration\ncan be set in the environment variable `LISTEN_GEM_ADAPTER_WARN_BEHAVIOR=warn|log|silent`.\n\n## Listen Adapters\n\nThe `Listen` gem has a set of adapters to notify it when there are changes.\n\nThere are 4 OS-specific adapters to support Darwin, Linux, \\*BSD and Windows.\nThese adapters are fast as they use some system-calls to implement the notifying function.\n\nThere is also a polling adapter - although it's much slower than other adapters,\nit works on every platform\u002Fsystem and scenario (including network filesystems such as VM shared folders).\n\nThe Darwin and Linux adapters are dependencies of the `listen` gem so they work out of the box. For other adapters a specific gem will have to be added to your Gemfile, please read below.\n\nThe `listen` gem will choose the best adapter automatically, if present. If you\nwant to force the use of the polling adapter, use the `:force_polling` option\nwhile initializing the listener.\n\n### On Windows\n\nIf you are on Windows, it's recommended to use the [`wdm`](https:\u002F\u002Fgithub.com\u002FMaher4Ever\u002Fwdm) adapter instead of polling.\n\nPlease add the following to your Gemfile:\n\n```ruby\ngem 'wdm', '>= 0.1.0'\n```\n\n### On \\*BSD\n\nIf you are on \\*BSD you can try to use the [`rb-kqueue`](https:\u002F\u002Fgithub.com\u002Fmat813\u002Frb-kqueue) adapter instead of polling.\n\nPlease add the following to your Gemfile:\n\n```ruby\ngem 'rb-kqueue', '>= 0.2'\n```\n\n### Getting the [polling fallback message](#options)?\n\nIf you see:\n```\nListen will be polling for changes.\n```\n\nThis means the Listen gem can’t find an optimized adapter. Typically this is caused by:\n\n- You’re on Windows and WDM gem isn’t installed.\n- You’re running the app without Bundler or RubyGems.\n- Using Sass which includes an ancient (the “dinosaur” type of ancient) version of the Listen gem.\n\nPossible solutions:\n\n1. Suppress the message by using the :force_polling option. Or, you could just ignore the message since it’s harmless.\n2. Windows users: Install the WDM gem.\n3. Upgrade Ruby (use RubyInstaller for Windows or RVM\u002Frbenv for Mac) and RubyGems.\n3. Run your apps using Bundler.\n4. Sass users: Install the latest version of Listen and try again.\n\n#### Simplified Bundler and Sass example\nCreate a Gemfile with these lines:\n```\nsource 'https:\u002F\u002Frubygems.org'\ngem 'listen'\ngem 'sass'\n```\nNext, use Bundler to update gems:\n```\n$ bundle update\n$ bundle exec sass --watch # ... or whatever app is using Listen.\n```\n\n### Increasing the amount of inotify watchers\n\nIf you are running Debian, RedHat, or another similar Linux distribution, run the following in a terminal:\n```\n$ sudo sh -c \"echo fs.inotify.max_user_watches=524288 >> \u002Fetc\u002Fsysctl.conf\"\n$ sudo sysctl -p\n```\nIf you are running ArchLinux, search the `\u002Fetc\u002Fsysctl.d\u002F` directory for config files with the setting:\n```\n$ grep -H -s \"fs.inotify.max_user_watches\" \u002Fetc\u002Fsysctl.d\u002F*\n\u002Fetc\u002Fsysctl.d\u002F40-max_user_watches.conf:fs.inotify.max_user_watches=100000\n```\nThen change the setting in the file you found above to a higher value (see [here](https:\u002F\u002Fwww.archlinux.org\u002Fnews\u002Fdeprecation-of-etcsysctlconf\u002F) for why):\n```\n$ sudo sh -c \"echo fs.inotify.max_user_watches=524288 > \u002Fetc\u002Fsysctl.d\u002F40-max-user-watches.conf\"\n$ sudo sysctl --system\n```\n\n#### The technical details\nListen uses `inotify` by default on Linux to monitor directories for changes.\nIt's not uncommon to encounter a system limit on the number of files you can monitor.\nFor example, Ubuntu Lucid's (64bit) `inotify` limit is set to 8192.\n\nYou can get your current inotify file watch limit by executing:\n```\n$ cat \u002Fproc\u002Fsys\u002Ffs\u002Finotify\u002Fmax_user_watches\n```\nWhen this limit is not enough to monitor all files inside a directory, the limit must be increased for Listen to work properly.\n\nYou can set a new limit temporarily with:\n```\n$ sudo sysctl fs.inotify.max_user_watches=524288\n$ sudo sysctl -p\n```\nIf you like to make your limit permanent, use:\n```\n$ sudo sh -c \"echo fs.inotify.max_user_watches=524288 >> \u002Fetc\u002Fsysctl.conf\"\n$ sudo sysctl -p\n```\nYou may also need to pay attention to the values of `max_queued_events` and `max_user_instances` if Listen keeps on complaining.\n\nWhile 524,288 is the maximum number of files that can be watched. Each file watch [takes up 1,080 bytes](https:\u002F\u002Fstackoverflow.com\u002Fa\u002F7091897\u002F1156119) on a 64-bit system, so assuming that all 524,288 watches are consumed, that allocates around 540 MiB.\nIf you're in an environment that is particularly memory-constrained, consider to specify a lower number.\n\n#### More info\nMan page for [inotify(7)](https:\u002F\u002Flinux.die.net\u002Fman\u002F7\u002Finotify).\nBlog post: [limit of inotify](https:\u002F\u002Fblog.sorah.jp\u002F2012\u002F01\u002F24\u002Finotify-limitation).\n\n### Issues and Troubleshooting\n\nIf the gem doesn't work as expected, start by setting `LISTEN_GEM_DEBUGGING=debug` or `LISTEN_GEM_DEBUGGING=info` as described above in [Logging and Debugging](#logging-and-debugging).\n\n*NOTE: without providing the output after setting the `LISTEN_GEM_DEBUGGING=debug` environment variable, it is usually impossible to guess why `listen` is not working as expected.*\n\n#### 3 steps before you start diagnosing problems\nThese 3 steps will:\n\n- help quickly troubleshoot obscure problems (trust me, most of them are obscure)\n- help quickly identify the area of the problem (a full list is below)\n- help you get familiar with listen's diagnostic mode (it really comes in handy, trust me)\n- help you create relevant output before you submit an issue (so we can respond with answers instead of tons of questions)\n\nStep 1 - The most important option in Listen\nFor effective troubleshooting set the `LISTEN_GEM_DEBUGGING=info` variable before starting `listen`.\n\nStep 2 - Verify polling works\nPolling has to work ... or something is really wrong (and we need to know that before anything else).\n\n(see force_polling option).\n\nAfter starting `listen`, you should see something like:\n```\nINFO -- : Record.build(): 0.06773114204406738 seconds\n```\nStep 3 - Trigger some changes directly without using editors or apps\nMake changes e.g. touch foo or echo \"a\" >> foo (for troubleshooting, avoid using an editor which could generate too many misleading events).\n\nYou should see something like:\n```\nINFO -- : listen: raw changes: [[:added, \"\u002Fhome\u002Fme\u002Ffoo\"]]\nINFO -- : listen: final changes: {:modified=>[], :added=>[\"\u002Fhome\u002Fme\u002Ffoo\"], :removed=>[]}\n```\n\"raw changes\" contains changes collected during the :wait_for_delay and :latency intervals, while \"final changes\" is what listen decided are relevant changes (for better editor support).\n\n## Performance\n\nIf `listen` seems slow or unresponsive, make sure you're not using the Polling adapter (you should see a warning upon startup if you are).\n\nAlso, if the directories you're watching contain many files, make sure you're:\n\n* not using Polling (ideally)\n* using `:ignore` and `:only` options to avoid tracking directories you don't care about (important with Polling and on MacOS)\n* running `listen` with the `:latency` and `:wait_for_delay` options not too small or too big (depends on needs)\n* not watching directories with log files, database files or other frequently changing files\n* not using a version of `listen` prior to 2.7.7\n* not getting silent crashes within `listen` (see `LISTEN_GEM_DEBUGGING=debug`)\n* not running multiple instances of `listen` in the background\n* using a file system with atime modification disabled (ideally)\n* not using a filesystem with inaccurate file modification times (ideally), e.g. HFS, VFAT\n* not buffering to a slow terminal (e.g. transparency + fancy font + slow gfx card + lots of output)\n* ideally not running a slow encryption stack, e.g. btrfs + ecryptfs\n\nWhen in doubt, `LISTEN_GEM_DEBUGGING=debug` can help discover the actual events and time they happened.\n\n## Tips and Techniques\n- Watch only directories you're interested in.\n- Set your editor to save quickly (e.g. without backup files, without atomic-save)\n- Tweak the `:latency` and `:wait_for_delay` options until you get good results (see [options](#options)).\n- Add `:ignore` rules to silence all events you don't care about (reduces a lot of noise, especially if you use it on directories)\n\n## Development\n\n* Documentation hosted at [RubyDoc](http:\u002F\u002Frubydoc.info\u002Fgithub\u002Fguard\u002Flisten\u002Fmaster\u002Fframes).\n* Source hosted at [GitHub](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten).\n\nPull requests are very welcome! Please try to follow these simple rules if applicable:\n\n* Please create a topic branch for every separate change you make.\n* Make sure your patches are well tested. All specs must pass on [CI](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Factions?workflow=Development).\n* Update the [Yard](http:\u002F\u002Fyardoc.org\u002F) documentation.\n* Update the [README](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fblob\u002Fmaster\u002FREADME.md).\n* Please **do not change** the version number.\n\nFor questions please join us in our [Google group](http:\u002F\u002Fgroups.google.com\u002Fgroup\u002Fguard-dev) or on\n`#guard` (irc.freenode.net).\n\n## Releasing\n\n### Prerequisites\n\n* You must have commit rights to the GitHub repository.\n* You must have push rights for rubygems.org.\n\n### How to release\n\n1. Run `bundle install` to make sure that you have all the gems necessary for testing and releasing.\n2.  **Ensure all tests are passing by running `bundle exec rake`.**\n3. Determine which would be the correct next version number according to [semver](http:\u002F\u002Fsemver.org\u002F).\n4. Update the version in `.\u002Flib\u002Flisten\u002Fversion.rb`.\n5. Update the version in the Install section of `.\u002FREADME.md` (`gem 'listen', '~> X.Y'`).\n6. Commit the version in a single commit, the message should be \"Preparing vX.Y.Z\"\n7. Run `bundle exec rake release:full`; this will tag, push to GitHub, and publish to rubygems.org.\n8. Update and publish the release notes on the [GitHub releases page](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Freleases) if necessary\n\n## Acknowledgments\n\n* [Michael Kessler (netzpirat)][] for having written the [initial specs](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fcommit\u002F1e457b13b1bb8a25d2240428ce5ed488bafbed1f).\n* [Travis Tilley (ttilley)][] for this awesome work on [fssm][] & [rb-fsevent][].\n* [Natalie Weizenbaum (nex3)][] for [rb-inotify][], a thorough inotify wrapper.\n* [Mathieu Arnold (mat813)][] for [rb-kqueue][], a simple kqueue wrapper.\n* [Maher Sallam][] for [wdm][], windows support wouldn't exist without him.\n* [Yehuda Katz (wycats)][] for [vigilo][], that has been a great source of inspiration.\n\n## Author\n\n[Thibaud Guillaume-Gentil](https:\u002F\u002Fgithub.com\u002Fthibaudgg) ([@thibaudgg](https:\u002F\u002Ftwitter.com\u002Fthibaudgg))\n\n## Contributors\n\n[https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fgraphs\u002Fcontributors](https:\u002F\u002Fgithub.com\u002Fguard\u002Flisten\u002Fgraphs\u002Fcontributors)\n\n[Thibaud Guillaume-Gentil (thibaudgg)]: https:\u002F\u002Fgithub.com\u002Fthibaudgg\n[Maher Sallam]: https:\u002F\u002Fgithub.com\u002FMaher4Ever\n[Michael Kessler (netzpirat)]: https:\u002F\u002Fgithub.com\u002Fnetzpirat\n[Travis Tilley (ttilley)]: https:\u002F\u002Fgithub.com\u002Fttilley\n[fssm]: https:\u002F\u002Fgithub.com\u002Fttilley\u002Ffssm\n[rb-fsevent]: https:\u002F\u002Fgithub.com\u002Fthibaudgg\u002Frb-fsevent\n[Mathieu Arnold (mat813)]: https:\u002F\u002Fgithub.com\u002Fmat813\n[Natalie Weizenbaum (nex3)]: https:\u002F\u002Fgithub.com\u002Fnex3\n[rb-inotify]: https:\u002F\u002Fgithub.com\u002Fnex3\u002Frb-inotify\n[stereobooster]: https:\u002F\u002Fgithub.com\u002Fstereobooster\n[rb-fchange]: https:\u002F\u002Fgithub.com\u002Fstereobooster\u002Frb-fchange\n[rb-kqueue]: https:\u002F\u002Fgithub.com\u002Fmat813\u002Frb-kqueue\n[Yehuda Katz (wycats)]: https:\u002F\u002Fgithub.com\u002Fwycats\n[vigilo]: https:\u002F\u002Fgithub.com\u002Fwycats\u002Fvigilo\n[wdm]: https:\u002F\u002Fgithub.com\u002FMaher4Ever\u002Fwdm\n","`listen` 是一个 Ruby 宝石，用于监听文件修改并通知用户相关变更。其核心功能包括检测文件的修改、新增和删除，并支持同时监控多个目录。该项目针对不同操作系统（如 Mac OS X 10.6+、Linux、*BSD 和 Windows）进行了优化，提高了在特定文件系统上的变更检测准确性。此外，它还允许使用正则表达式模式来忽略某些路径，从而提高准确性和速度。`listen` 非常适合需要实时响应文件系统变化的应用场景，例如开发环境下的自动构建工具或持续集成服务。需要注意的是，当前版本不完全支持符号链接目录及一些特定类型的文件系统可能需要启用轮询机制才能正常工作。",2,"2026-06-11 03:16:01","top_language"]